Details
-
Type:
New Feature
-
Status: Open (View Workflow)
-
Priority:
Major
-
Resolution: Unresolved
-
Component/s: git-plugin
-
Labels:
-
Similar Issues:
Description
It would be nice to be able to use the GitPublisher inside a workflow as it is possible in other jobs.
This requires the plugin to be upgrade to Jenkins core 1.580.1+, to implement the jenkins.tasks.SimpleBuildStep in GitPublisher
Attachments
Issue Links
- depends on
-
JENKINS-26055 DurableTaskStep
-
- Reopened
-
- is duplicated by
-
JENKINS-42279 Provide a command to commit on a scm inside a pipeline, like there is a checkout command
-
- Resolved
-
-
JENKINS-47733 Add a withGit pipeline step that provides git credentials
-
- Closed
-
- is related to
-
JENKINS-36496 Publish from pipeline
-
- Closed
-
Activity
Field | Original Value | New Value |
---|---|---|
Labels | workflow |
Issue Type | Improvement [ 4 ] | New Feature [ 2 ] |
Priority | Trivial [ 5 ] | Major [ 3 ] |
Summary | Be able to use GitPublisher in a workflow description | Be able to use GitPublisher in a workflow |
Summary | Be able to use GitPublisher in a workflow | Step to run Git commands w/ credentials & tool (was: GitPublisher support) |
Assignee | Nicolas De Loof [ ndeloof ] |
Link | This issue depends on JENKINS-26055 [ JENKINS-26055 ] |
Rank | Ranked higher |
Link |
This issue is related to |
Workflow | JNJira [ 163171 ] | JNJira + In-Review [ 181120 ] |
Labels | workflow | pipeline workflow |
Labels | pipeline workflow | pipeline |
Link |
This issue is duplicated by |
Link |
This issue is related to |
Summary | Step to run Git commands w/ credentials & tool (was: GitPublisher support) | Pipeline step to run Git commands with credentials & tool |
Link |
This issue is duplicated by |
Link |
This issue is related to |
I already considered this possibility but do not consider it straightforward. GitPublisher relies on obtaining the single GitSCM configured for the project; there is no equivalent concept for Workflow.
Anyway the extensive hardcoded logic in this publisher probably does not make sense in an otherwise flexible script. More useful would be an independent Step which lets you run arbitrary git commands, integrates with Credentials for authentication, and lets you pick a GitTool (certainly CLI, perhaps also JGit).