https://pfspipe.ipmu.jp/jira This file is an XML representation of an issue en-us 8.3.4 803005 13-09-2019 https://pfspipe.ipmu.jp/jira/browse/PIPE2D-429 DRP 2-D Pipeline <p>If I tag a particular pfs_pipe2d commit twice, Jenkins builds don't fire on the second tag. See <a href="https://stackoverflow.com/a/45149784/834250" class="external-link" rel="nofollow">https://stackoverflow.com/a/45149784/834250</a> . We may need to workaround this, or make new (empty) commits for the tag.</p> PIPE2D-429

Fix Jenkins builds on double tags

Story Normal Won't Fix Won't Fix price price Wed, 22 May 2019 18:43:09 +0000 Tue, 16 Jun 2020 18:27:07 +0000 Tue, 16 Jun 2020 18:27:07 +0000 0 1 <p>A simple workaround is to make an empty git commit and tag that:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> git commit --allow-empty -m <span class="code-quote">"Release MM.mm.pp"</span> git push git tag MM.mm.pp -m <span class="code-quote">"Release after merging PIPE2D-whatever"</span> git push origin MM.mm.pp </pre> </div></div> <p>CSES have installed a new Jenkins plugin that may make this unnecessary.</p> <p>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.</p> <p>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.</p> <p>We switched to a script-based trigger in <a href="https://pfspipe.ipmu.jp/jira/browse/PIPE2D-544" title="For releases, apply tags to each repository" class="issue-link" data-issue-key="PIPE2D-544"><del>PIPE2D-544</del></a>.</p> Development Rank 0|zzs009: