[PIPE2D-429] Fix Jenkins builds on double tags Created: 23/May/19 Updated: 17/Jun/20 Resolved: 17/Jun/20 |
|
| Status: | Won't Fix |
| Project: | DRP 2-D Pipeline |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | Normal |
| Reporter: | price | Assignee: | price |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
If I tag a particular pfs_pipe2d commit twice, Jenkins builds don't fire on the second tag. See https://stackoverflow.com/a/45149784/834250 . We may need to workaround this, or make new (empty) commits for the tag. |
| Comments |
| Comment by price [ 01/Jun/19 ] |
|
A simple workaround is to make an empty git commit and tag that: git commit --allow-empty -m "Release MM.mm.pp" git push git tag MM.mm.pp -m "Release after merging PIPE2D-whatever" git push origin MM.mm.pp CSES have installed a new Jenkins plugin that may make this unnecessary. |
| Comment by price [ 12/Sep/19 ] |
|
I have repeatedly looked for a solution to this problem, and haven't found anything straightforward that uses the version of Jenkins that CSES has deployed. One possibility is that we could switch to a script-based trigger. The script would probably only work within the Princeton firewall, and possibly only within CSES; authentication may be required. |
| Comment by price [ 17/Jun/20 ] |
|
We switched to a script-based trigger in |