code change is the only thing being watched for right now, if you do a
git commit --amend --no-edit it will give your commit a new hash and you
can force push which should trigger a jenkins to build it again

-Jake

On Tue, Apr 19, 2016 at 10:57 AM, Jim King <[email protected]> wrote:

> It looks like 428 and 431 went through.
> How do I ask github to kick a new build cycle on:
> https://github.com/apache/thrift/pull/981
> without submitting a code change?
>
> - Jim
>
> -----Original Message-----
> From: Jake Farrell [mailto:[email protected]]
> Sent: Tuesday, April 19, 2016 9:46 AM
> To: [email protected]
> Cc: [email protected]
> Subject: Re: Apache Jenkins builds are still broken
>
> I started taking a look at this earlier this morning and made some changes,
> #430 is running right now, but then hit an odd error with 431 with git
> error
>
> org.eclipse.jgit.errors.TransportException:
> channel:/home/jenkins/jenkins-slave/workspace/Thrift-precommit: Pipe is
> already closed
>
> waiting for all concurrent builds to finish and will kick off again
>
> On Tue, Apr 19, 2016 at 9:14 AM, Jim King <[email protected]> wrote:
>
> > https://builds.apache.org/job/Thrift-precommit/429/
> >
> >
> >
> > Merging refs/tags/changes/429
> >
> >  > git rev-parse refs/tags/changes/429^{commit} # timeout=10
> >
> > FATAL: Command "git rev-parse refs/tags/changes/429^{commit}" returned
> status code 128:
> >
> > stdout: refs/tags/changes/429^{commit}
> >
> >
> >
> > stderr: fatal: ambiguous argument 'refs/tags/changes/429^{commit}':
> unknown revision or path not in the working tree.
> >
> > Use '--' to separate paths from revisions, like this:
> >
> > 'git <command> [<revision>...] -- [<file>...]'
> >
> >
> >
> > hudson.plugins.git.GitException <
> http://stacktrace.jenkins-ci.org/search?query=hudson.plugins.git.GitException>:
> Command "git rev-parse refs/tags/changes/429^{commit}" returned status code
> 128:
> >
> > stdout: refs/tags/changes/429^{commit}
> >
> >
> >
> > stderr: fatal: ambiguous argument 'refs/tags/changes/429^{commit}':
> unknown revision or path not in the working tree.
> >
> > Use '--' to separate paths from revisions, like this:
> >
> > 'git <command> [<revision>...] -- [<file>...]'
> >
> >
> >
> >         at
> > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAP
> > IImpl.java:1693)
> >
> >         at
> > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAP
> > IImpl.java:1669)
> >
> >         at
> > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAP
> > IImpl.java:1665)
> >
> >         at
> > org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPII
> > mpl.java:1307)
> >
> >
> >
> >
> >
> > [image: Description: Description: simplivity-lg-xsmall]
> >
> > James E. King, III
> >
> > Architect
> >
> > 8 Technology Drive, 2nd Floor
> > Westborough, MA 01581-1756
> >
> > Ph: 855-SVT-INFO
> >
> >
> >
> >
> > ------------------------------
> > PRIVACY STATEMENT:
> > This message is a PRIVATE communication. This message and all
> > attachments are a private communication sent by SimpliVity and are
> > considered to be confidential or protected by privilege. If you are
> > not the intended recipient, you are hereby notified that any
> > disclosure, copying, distribution or use of the information contained
> > in or attached to this message is strictly prohibited. Please notify
> > the sender of the delivery error by replying to this message, and then
> delete it from your system.
> > For more information please visit http://www.simplivity.com
> > ------------------------------
> >
>
> ---------------------------------------------------------------------------------------
> PRIVACY STATEMENT:
> This message is a PRIVATE communication.  This message and all attachments
> are a private communication sent by SimpliVity and are considered to be
> confidential or protected by privilege. If you are not the intended
> recipient, you are hereby notified that any disclosure, copying,
> distribution or use of the information contained in or attached to this
> message is strictly prohibited.  Please notify the sender of the delivery
> error by replying to this message, and then delete it from your system.
>
> ---------------------------------------------------------------------------------------
>

Reply via email to