[JIRA] [build-pipeline] (JENKINS-23524) Build Pipeline does not discover downstream promoted jobs?
Mark Wigzell created JENKINS-23524 Build Pipeline does not discover downstream promoted jobs? Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: build-pipeline Created: 21/Jun/14 12:02 AM Description: I installed Build Pipeline and tried it on my jobs. They work by invoking a build as a promotion action. I was disappointed that the pipeline view failed to follow my builds except where there was a direct chain of automatic chained jobs. I guess perhaps my expectation doesn't match the pipeline concept? Or perhaps my build flow is not a pipeline? Basically, we have a continuous build job which allows a selected build to be promoted. The promotion action causes another build to be executed. Generally we do not have an automatic build chain, but a manual promotion chain. This approach works better for us, since we don't have to maintain (and archive) any build history unless a build is promoted. Perhaps my expectation is in error, however I think it would be a great enhancement to a great plugin! Environment: Jenkins 1.554, Build Pipeline version 1.4.3 Project: Jenkins Labels: promoted-build-chain Priority: Major Reporter: Mark Wigzell 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/d/optout.
[JIRA] [copyartifact] (JENKINS-14999) Copy Artifact plugin: Unable to find project for artifact copy when using a build parameter
Mark Wigzell reopened JENKINS-14999 Copy Artifact plugin: Unable to find project for artifact copy when using a build parameter Hi I wish to reopen this bug since it is actually a bug for a different reason, namely that the use has access to the selected job if he doesn't use dynamic project name, but hard codes it instead. The fact that one must enable read access for specifying a project via a dynamic variabe vs. specifying it in a hardcoded fashion indicates there is a bug in copy artifacts which should forbid the access unless the authenticated group is added with read permissions for jobs. (This is a very badly documented feature, and has caused me no end of trouble) Change By: Mark Wigzell (01/Aug/13 8:31 PM) Resolution: NotADefect Status: Resolved Reopened 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] [deploy] (JENKINS-18991) Unable to access debian package 1.525 using apt-get or browse http://pkg.jenkins-ci.org/debian fails
Mark Wigzell created JENKINS-18991 Unable to access debian package 1.525 using apt-get or browse http://pkg.jenkins-ci.org/debian fails Issue Type: Bug Assignee: Unassigned Components: deploy Created: 29/Jul/13 9:14 PM Description: try to run apt-get install jenkins=1.525 or try browse to http://pkg.jenkins-ci.org/debian and access jenkins_1.525_all.deb it fails, 404 file not found Environment: ubuntu apt-get debian jenkins_1.525_all.deb Project: Jenkins Labels: 404 debian apt-get Priority: Major Reporter: Mark Wigzell 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] (JENKINS-16075) Lint icon not shown when selecting a particular build
Mark Wigzell commented on JENKINS-16075 Lint icon not shown when selecting a particular build a href=""img height="24" style="margin: 2px;" alt="" width="24" src="" //a a href=""Lint Issues/a/divdiv class="task" You can see that the ref to /static/06707550 is doubled. 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] (JENKINS-16075) Lint icon not shown when selecting a particular build
Mark Wigzell reopened JENKINS-16075 Lint icon not shown when selecting a particular build Installed 1.505 Jenkins with 2.0.3 of Android Lint plugin, lint icon still broken. Reason is that the root of the icon path is doubled in the actual HTML for the respective pages in Jenkins build display. Change By: Mark Wigzell (12/Mar/13 9:09 PM) Resolution: Fixed Status: Closed Reopened 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.
