[JIRA] [core] (JENKINS-15156) Builds disappear from build history after completion
Pavel Kudrys edited a comment on JENKINS-15156 Builds disappear from build history after completion Hello, I'm using Jenkins v 1.517 and I'm experiencing a very similar (if not the same) problem. All builds are visible on the master machine but older builds, from time to time, simply disappears from the list of builds on the slave machine. Is this problem fixed in actual or upcoming version? Please see the attached screenshot (disappeared history of builds on slave machine). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [core] (JENKINS-15156) Builds disappear from build history after completion
Pavel Kudrys updated JENKINS-15156 Builds disappear from build history after completion This screenshot shows disappeared history of builds on slave machine. Change By: Pavel Kudrys (10/Jun/13 6:43 AM) Attachment: Jenkins_lost_build_history.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [core] (JENKINS-15156) Builds disappear from build history after completion
Pavel Kudrys edited a comment on JENKINS-15156 Builds disappear from build history after completion Hello, I'm using Jenkins v 1.517 and I'm experiencing a very similar (if not the same) problem. All builds are visible on the master machine but older builds, from time to time, simply disappears from the list of builds on the slave machine. Please see the attached screenshot (disappeared history of builds on slave machine). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [maven] (JENKINS-18183) After upgrading from jenkins 1.513 to 1.515, I cannot use Settings file (Settings file in filesystem) field in a maven prebuild step for a maven project.
Tony Bridges commented on JENKINS-18183 After upgrading from jenkins 1.513 to 1.515, I cannot use Settings file (Settings file in filesystem) field in a maven prebuild step for a maven project. I have the same issue in the postbuild step. When we upgraded from 1513 to 1517, the values reset themselves to "use default maven settings" and we cannot change them back to use the managed settings file that administers our repository credentials. Has anyone made progress on this issue ? It's a significant regression. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-18089) block() generates invalid config, documentation is ambiguous
Justin Ryan resolved JENKINS-18089 as Fixed block() generates invalid config, documentation is ambiguous Change By: Justin Ryan (09/Jun/13 7:36 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-18089) block() generates invalid config, documentation is ambiguous
Justin Ryan commented on JENKINS-18089 block() generates invalid config, documentation is ambiguous Fixed in https://github.com/jenkinsci/job-dsl-plugin/pull/57. It should be in the next release, 1.16, of the plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-18089) block() generates invalid config, documentation is ambiguous
Justin Ryan started work on JENKINS-18089 block() generates invalid config, documentation is ambiguous Change By: Justin Ryan (09/Jun/13 7:29 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-18089) block() generates invalid config, documentation is ambiguous
Justin Ryan commented on JENKINS-18089 block() generates invalid config, documentation is ambiguous You're right that the docs are incorrect, even though you were looking at a fork of the project under andrewharmellaw. Please refer to the official docs in the future: https://github.com/jenkinsci/job-dsl-plugin/wiki/Job-reference and https://github.com/jenkinsci/job-dsl-plugin/wiki/Job-DSL-Commands. I've fix the docs, simply enough. The code is wrong too. I'm working on a fix. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-18076) Methods to import and read files from the workspace (even if remote).
Justin Ryan resolved JENKINS-18076 as Fixed Methods to import and read files from the workspace (even if remote). This is merged on now, just not documented yet. This si the method signature: InputStream streamFileInWorkspace(String filePath) throws IOException; String readFileInWorkspace(String filePath) throws IOException; Change By: Justin Ryan (09/Jun/13 7:14 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [git] (JENKINS-17413) Unhelpful exception caused by a NullPointerException while attempting to use a git refspec -- javax.servlet.ServletException: java.lang.RuntimeException: Failed to instant
Karl Goldstein commented on JENKINS-17413 Unhelpful exception caused by a NullPointerException while attempting to use a git refspec -- javax.servlet.ServletException: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.git.GitSCM Just got an NPE on the same line: hudson.plugins.git.GitSCM.(GitSCM.java:250) I was trying to specify a non-default branch to build, not a refspec. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [warnings] (JENKINS-17925) StyleCop Parser Fails with Exception: Content is not allowed in prolog
Ulli Hafner assigned JENKINS-17925 to Sebastian Seidl StyleCop Parser Fails with Exception: Content is not allowed in prolog Change By: Ulli Hafner (09/Jun/13 3:43 PM) Assignee: Ulli Hafner Sebastian Seidl This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [build-pipeline] (JENKINS-18162) Parameterized downstream project is missing upstream-set parameters when used by mutliple upstream projects
Ole Christian Langfjæran commented on JENKINS-18162 Parameterized downstream project is missing upstream-set parameters when used by mutliple upstream projects 1.3.4-SNAPSHOT is indeed bugged with the run button, the retry being the most importent one I think. https://issues.jenkins-ci.org/browse/JENKINS-11105. But passing parameters seems to work for me, unless i do a retry. Using 1.3.4-SNAPSHOT a new "Manual build other projects" is available. Can't remember the exact name as I'm on sickleave for a month from the project. But for the build that is manually triggered, the "triggering" project has to transfer the parameters to the build a second time. As an example if your manual build is a parameterized build with the parameter VERSION, you have to repeat it like so: VERSION=$VERSION Even if the first triggered build had the parameter with exact same name. At least, that's what I've experienced. Hope it helps, and hope a 1.3.4 version could be tagged and uploaded soon. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [core] (JENKINS-18266) Generate unique id that will be kept after leaving the queue and starting to run the job
Amos Sonnenwirth created JENKINS-18266 Generate unique id that will be kept after leaving the queue and starting to run the job Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: core Created: 09/Jun/13 9:03 AM Description: There should be a unique id of a started job that will be kept all the way, from the phase that it enter the queue till the phase it completed its run. This unique id should be returned as part of the returned data when starting a new build with parameters and later on being able to query the job status according this unique id Due Date: 11/Jun/13 12:00 AM Environment: Related to all platforms Fix Versions: current Project: Jenkins Labels: jenkins Priority: Major Reporter: Amos Sonnenwirth This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-18076) Methods to import and read files from the workspace (even if remote).
Justin Ryan commented on JENKINS-18076 Methods to import and read files from the workspace (even if remote). Keeping in mind the goal of being to run the DSL scripts outside of Jenkins, I probably won't inject a workspace variable. But instead create a method like readFile. That should be able to work remotely, locally and in Jenkins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-18076) Methods to import and read files from the workspace (even if remote).
Justin Ryan started work on JENKINS-18076 Methods to import and read files from the workspace (even if remote). Change By: Justin Ryan (09/Jun/13 7:44 AM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-18251) Add support for "Do not fail build if archiving returns nothing" option of archiveArtifacts publisher
Justin Ryan assigned JENKINS-18251 to Chris Dore Add support for "Do not fail build if archiving returns nothing" option of archiveArtifacts publisher Chris, this all looks fine. The method signature looks good, the 18251 branch looks good. I'm not sure why it's complaining. It's specifically mentioning a null value. You might have to set some debug point and see exactly what the XML looks like when running in Jenkins (vs a unit test). For reference, this is the branch: https://github.com/oesolutions/job-dsl-plugin/commit/18251 Change By: Justin Ryan (09/Jun/13 7:43 AM) Assignee: Justin Ryan Chris Dore This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-18075) Add method to schedule a job after it has been created/modified
Justin Ryan commented on JENKINS-18075 Add method to schedule a job after it has been created/modified It'll be in 1.16. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-18075) Add method to schedule a job after it has been created/modified
Justin Ryan
resolved JENKINS-18075 as Fixed
Add method to schedule a job after it has been created/modified
I added a queue(String jobName) and queue(Job job) method. You can now do the following to queue up JobA and JobB:
def jobA = job {
name 'JobA'
}
queue jobA
queue 'JobB'
Change By:
Justin Ryan
(09/Jun/13 7:29 AM)
Status:
In Progress
Resolved
Resolution:
Fixed
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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/groups/opt_out.
