Comments (6)
i dont think i understand the request here. it sounds like your desired workflow is outside the normal expectation of what this gitlab plugin was designed for. since you have already built a plugin related to your workflow, i'm wondering why you wouldnt just handle the additional need you describe directly from within your custom plugin. could you help me understand what i am overlooking?
from gitlab.
Ideally for separation of concerns. I don't want my plugin to try to do too much, just a merge request, nothing else + while this plugin already exists and is 250+ star battle-tested.
I just need to be able to specify the target repo using the project ID, instead of having it try to infer the target based on the current repo, which for a plugin that aims to be the generic semantic-release Gitlab deployment doesn't sound too weird of a request
I.E. just an optional PROJECT_ID parameter
from gitlab.
The workflow is indeed a bit special, but I think allowing to pass a project ID would be symmetrical to the existing possibility to pass a GITLAB_URL
or GITLAB_PREFIX
.
from gitlab.
The workflow is indeed a bit special, but I think allowing to pass a project ID would be symmetrical to the existing possibility to pass a
GITLAB_URL
orGITLAB_PREFIX
.
Sounds like a valid option. The function get-repo-id couldbe adjusted and it could be allowed to provide a GITLAB_PROJECT_ID
or similar
from gitlab.
The workflow is indeed a bit special, but I think allowing to pass a project ID would be symmetrical to the existing possibility to pass a
GITLAB_URL
orGITLAB_PREFIX
.
Looking at the code @JonasSchubert referenced, wouldn't setting the env var CI_PROJECT_PATH
solve this then? It seems to first try to infer from that variable and as a fallback the git url.
from gitlab.
The workflow is indeed a bit special, but I think allowing to pass a project ID would be symmetrical to the existing possibility to pass a
GITLAB_URL
orGITLAB_PREFIX
.Looking at the code @JonasSchubert referenced, wouldn't setting the env var
CI_PROJECT_PATH
solve this then? It seems to first try to infer from that variable and as a fallback the git url.
Only partially, because it'll only be evaluated when running within GitLab CI (the service === "gitlab"
condition).
from gitlab.
Related Issues (20)
- ERR_REQUIRE_ESM error with semantic-release-monorepo HOT 3
- GitLab release is not being created HOT 5
- BUG: generic_package upload causes Error 400 on release creation HOT 2
- better use version instead of git tag for publishing generic package? HOT 6
- bug: @semantic-release is using github instaed of gitlab HOT 1
- Documentation clarification and token usage with dry run HOT 1
- Link to external artifacts in release? HOT 1
- An error occurred while running semantic-release: Error: Command failed with exit code 128: HOT 3
- Generated links use legacy routes and stopped working HOT 3
- Use CI_PROJECT_ID instead of name of the project in API calls HOT 9
- How to include reference to docker image (or arbitrary markdown) as part of release message HOT 1
- Inspect Submodule changes HOT 2
- feature request: Allow dryrun to execute even in Merge request pipeline (avoid duplicated pipelines) HOT 3
- Error: self-signed certificate in certificate chain HOT 2
- support updating changelog in repo HOT 1
- The gitlab API merge request URL has an additional single quote HOT 8
- Release asset URLs are incorrect HOT 3
- Possibility to send succesMessage only for Issue HOT 5
- Feature: Catch error "Project must have a description" when creating a release. HOT 10
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from gitlab.