Unfortunately, the setting for "branches to build " is set to an actual branch in my case, so it doesn't look like this is the case.
Thanks, Greg On Nov 4, 2011, at 10:54 AM, Konstantin Komissarchik wrote: > I ran into this exact issue earlier. Take a look in your job configuration > under "branches to build" for git. If it shows "**" in the text box, erase > that setting and save your job. You should be able to trigger your job > without any issues. Note that at least for me, loading the configuration > subsequently will list branch to build as master in the same field. > > This started happening for me after the last Hudson upgrade. Likely a bug > and/or a migration issue in the Git plugin. > > - Konstantin > > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Greg > Watson > Sent: Friday, November 04, 2011 7:43 AM > To: Cross project issues > Subject: [cross-project-issues-dev] hudson question > > Hi, > > Is there a way to force hudson to build even if there are no change to the > project repo? If the hudson build fails for some reason and I manually > restart the build, it fails because there are no changes: > > Started by remote host 0:0:0:0:0:0:0:1 > Building remotely on hudson-slave1 > Checkout:ptp-release / /opt/users/hudsonbuild/workspace/ptp-release - > hudson.remoting.Channel@784f05d1:hudson-slave1 > Using strategy: Default > Last Built Revision: Revision acbba640675ad551a739600e45793c472763c92c > (origin1/ptp_5_0) > Checkout:ptp-release / /opt/users/hudsonbuild/workspace/ptp-release - > hudson.remoting.LocalChannel@510051e3 > Fetching changes from the remote Git repository > Fetching upstream changes from > git://git.eclipse.org/gitroot/ptp/org.eclipse.ptp.git > Seen branch in repository origin1/master > Seen branch in repository origin1/ptp_1_0 > Seen branch in repository origin1/ptp_1_1 > Seen branch in repository origin1/ptp_2_0 > Seen branch in repository origin1/ptp_2_1 > Seen branch in repository origin1/ptp_3_0 > Seen branch in repository origin1/ptp_4_0 > Seen branch in repository origin1/ptp_4_1 > Seen branch in repository origin1/ptp_5_0 > Nothing to do > Checkout:photran / /opt/users/hudsonbuild/workspace/ptp-release/photran - > hudson.remoting.LocalChannel@510051e3 > Fetching changes from the remote Git repository > Fetching upstream changes from > git://git.eclipse.org/gitroot/ptp/org.eclipse.photran.git > Seen branch in repository origin/master > Seen branch in repository origin/photran_4_0 > Seen branch in repository origin/photran_5_0 > Seen branch in repository origin/ptp_4_0 > Seen branch in repository origin/ptp_4_1 > Seen branch in repository origin/ptp_5_0 > Nothing to do > Archiving artifacts > Sending e-mails to: [email protected] > [DEBUG] Skipping watched dependency update for build: ptp-release #29 due to > result: FAILURE > Finished: FAILURE > > The only way to get it to restart is to make an artificial change in a file > and commit that to the repo. Any suggestions welcome. > > Greg > _______________________________________________ > cross-project-issues-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > > _______________________________________________ > cross-project-issues-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev _______________________________________________ cross-project-issues-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
