[JIRA] [core] (JENKINS-30899) Build History order not sorted properly
Title: Message Title Tim College commented on JENKINS-30899 Re: Build History order not sorted properly I have an issue with the Build History section, though it's slightly different - mine are actually in the correct order, but many of the most recent builds are missing. For example, in one job, the most recent build is 973 - the most recent shown in the history is 954. In another, the most recent is 1837, but the most recent shown is just 1787. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-30899) Build History order not sorted properly
Title: Message Title Tim College commented on JENKINS-30899 Re: Build History order not sorted properly Downgrading to 1.632 solves the "missing a bunch of recent builds" issue I mentioned above. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-plugin] (JENKINS-30890) Getting "java.lang.ClassNotFoundException: com.jcraft.jsch.Buffer" error
Title: Message Title Tim College commented on JENKINS-30890 Re: Getting "java.lang.ClassNotFoundException: com.jcraft.jsch.Buffer" error Confirmed here, too. Now to Google "how to downgrade Jenkins" Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-plugin] (JENKINS-30890) Getting "java.lang.ClassNotFoundException: com.jcraft.jsch.Buffer" error
Title: Message Title
Tim College commented on JENKINS-30890
Re: Getting "java.lang.ClassNotFoundException: com.jcraft.jsch.Buffer" error
Thanks. I'm on redhat, and the solution there is:
{{yum downgrade jenkins }}
Followed by disabling the repo for now.
Downgrading fixes the issue for me, as well.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-plugin] (JENKINS-30890) Getting "java.lang.ClassNotFoundException: com.jcraft.jsch.Buffer" error
Title: Message Title
Tim College edited a comment on JENKINS-30890
Re: Getting "java.lang.ClassNotFoundException: com.jcraft.jsch.Buffer" error
Thanks. I'm on redhat, and the solution there is:{{ yum downgrade jenkins}}Followed by disabling the repo for now. Downgrading fixes the issue for me, as well.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-plugin] (JENKINS-30890) Getting "java.lang.ClassNotFoundException: com.jcraft.jsch.Buffer" error
Title: Message Title
Tim College edited a comment on JENKINS-30890
Re: Getting "java.lang.ClassNotFoundException: com.jcraft.jsch.Buffer" error
Thanks. I'm on redhat, and the solution there is: { { noformat} yum downgrade jenkins {noformat } } Followed by disabling the repo for now. Downgrading fixes the issue for me, as well.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [scripttrigger-plugin] (JENKINS-29918) $WORKSPACE has stopped working in ScriptTrigger shell script
Title: Message Title
Tim College created an issue
Jenkins / JENKINS-29918
$WORKSPACE has stopped working in ScriptTrigger shell script
Issue Type:
Bug
Assignee:
Gregory Boissinot
Components:
scripttrigger-plugin
Created:
12/Aug/15 4:20 PM
Environment:
Jenkins 1.624
Priority:
Major
Reporter:
Tim College
I have jobs that monitor the status of external projects. These look for the latest version, and compare it to a known version. The known version is tracked in a file in the workspace.
Unfortunately, sometime between July 11 (the last successful build) and August 9 (when I noticed it didn't work) the $WORKSPACE variable has stopped being available in the environment when the ScriptTrigger script is run. This ends up meaning my jobs are now looking in the wrong place. Since looking in the wrong place wound up exiting non-zero, the result was don't run, which meant I didn't notice something was wrong until the team noticed that an external project had been updated and our Jenkins jobs didn't trigger.
I'm able to use a combination of $ {JENKINS_HOME}
/workspace/$ {JOB_NAME}
to re-create the path, but that's a lot less clear, contains a hard-coded value, and I'd rather not have to update dozens of jobs manually.
[JIRA] [scripttrigger-plugin] (JENKINS-29918) $WORKSPACE has stopped working in ScriptTrigger shell script
Title: Message Title
Tim College updated an issue
Jenkins / JENKINS-29918
$WORKSPACE has stopped working in ScriptTrigger shell script
Change By:
Tim College
Ihavejobsthatmonitorthestatusofexternalprojects.Theselookforthelatestversion,andcompareittoaknownversion.Theknownversionistrackedinafileintheworkspace.Unfortunately,sometimebetweenJuly11(thelastsuccessfulbuild)andAugust9(whenI*noticed*itdidn'twork)the$WORKSPACEvariablehasstoppedbeingavailableintheenvironmentwhentheScriptTriggerscriptisrun.Thisendsupmeaningmyjobsarenowlookinginthewrongplace.Sincelookinginthewrongplacewoundupexitingnon-zero,theresultwasdon'trun,whichmeantIdidn'tnoticesomethingwaswronguntiltheteamnoticedthatanexternalprojecthadbeenupdatedandourJenkinsjobsdidn'ttrigger.I'mabletouseacombinationof {{' ${JENKINS_HOME}/workspace/${JOB_NAME} '}} tore-createthepath,butthat'salotlessclear,containsahard-codedvalue,andI'drathernothavetoupdatedozensofjobsmanually.Ifthiswaschangedonpurpose,canyouexplainwhy,orlinktodocumentationthatexplainsit?Iwasn'tabletodetermine.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [scripttrigger-plugin] (JENKINS-29918) $WORKSPACE has stopped working in ScriptTrigger shell script
Title: Message Title
Tim College updated an issue
Jenkins / JENKINS-29918
$WORKSPACE has stopped working in ScriptTrigger shell script
Change By:
Tim College
Ihavejobsthatmonitorthestatusofexternalprojects.Theselookforthelatestversion,andcompareittoaknownversion.Theknownversionistrackedinafileintheworkspace.Unfortunately,sometimebetweenJuly11(thelastsuccessfulbuild)andAugust9(whenI*noticed*itdidn'twork)the$WORKSPACEvariablehasstoppedbeingavailableintheenvironmentwhentheScriptTriggerscriptisrun.Thisendsupmeaningmyjobsarenowlookinginthewrongplace.Sincelookinginthewrongplacewoundupexitingnon-zero,theresultwasdon'trun,whichmeantIdidn'tnoticesomethingwaswronguntiltheteamnoticedthatanexternalprojecthadbeenupdatedandourJenkinsjobsdidn'ttrigger.I'mabletouseacombinationof{{'$ { JENKINS_HOME } /workspace/$ { JOB_NAME } '}}tore-createthepath,butthat'salotlessclear,containsahard-codedvalue,andI'drathernothavetoupdatedozensofjobsmanually.Ifthiswaschangedonpurpose,canyouexplainwhy,orlinktodocumentationthatexplainsit?Iwasn'tabletodetermine.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
