[JIRA] [jira-plugin] (JENKINS-750) Possibility to update custom fields
Title: Message Title Martin Meyer commented on JENKINS-750 Re: Possibility to update custom fields Radek Antoniuk, yes, that's correct. I was assuming the possibility to update custom fields would also imply setting them for creation... Considering this issue was created back in 2007, I won't mind opening a new one for the moment 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] [jira-plugin] (JENKINS-750) JIRA plugin: put build number in custom field?
Title: Message Title Martin Meyer commented on JENKINS-750 Re: JIRA plugin: put build number in custom field? Is there any update on this? I'm having the problem that we're using Tempo-Plugin which introduces a mandatory field Account to all projects. It must be set explicitly when creating new issues, so the plugin won't work at all. I would need to be able to specify a value for this field for creating new issues... 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] [maven-plugin] (JENKINS-10382) Can not use jenkins Environment variable to parameterize maven Profile via -P option
Martin Meyer commented on JENKINS-10382 Can not use jenkins Environment variable to parameterize maven Profile via -P option Any update on this? This was created in 2011 and still not working. Note: Obviously, this affects all env variable substitution in the maven build step, not just to specify a profile... 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] [parameterized-trigger] (JENKINS-24860) Allow to disable build trigger
Martin Meyer commented on JENKINS-24860 Allow to disable build trigger Usecase: As mentioned in my second commant, we're using the plugin in combination with the pipeline view to build deployment pipelines, so we'd have deployment jobs (deploy_job1, deplob_job2, deplob_job2) that are chained by the trigger plugin (so job1 triggers job2 and so on). If we want to deploy ONLY to platform 1 (deploy_job1), we need to disable the triggering of deploy_job2. In other words, we regularly need to interrupt a deployment pipeline. And that's where a disabled state would come in very handy. It would be useful because we wouldn't have to delete and re-configer the trigger and we could avoid installing / using additional plugins like the ones recommended by you... 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] [parameterized-trigger] (JENKINS-24860) Allow to disable build trigger
Martin Meyer commented on JENKINS-24860 Allow to disable build trigger Thanks for the feedback. I think easyness of implementation along with usefulness should influence development (so you certainly SHOULD take easyness into consideration as well). Anyway, I tried out the flexible publish plugin and it actually does what I want. It even works with the build pipeline plugin (even though I wouldn't see the Run? condition there but that's a (visual) build pipeline plugin issue... I still feel that a 'Disabled' option would be quite a natural extension to the already present options of the plugin (genreally, if you have 'always', you might as well have 'never'). But I can live with the flexible publish 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/d/optout.
[JIRA] [parameterized-trigger] (JENKINS-24860) Allow to disable build trigger
Martin Meyer commented on JENKINS-24860 Allow to disable build trigger Hm, it feels like adding a Disabled option to the plugin would be really easy. We're using the plugin in combination with the Pipeline view. I'm not sure if the view would pick up the association with the triggered project correctly if it was nested inside of other plugins like the ones you mentioned (haven't tested it, though). 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] [parameterized-trigger] (JENKINS-24860) Allow to disable build trigger
Martin Meyer created JENKINS-24860 Allow to disable build trigger Issue Type: Improvement Assignee: huybrechts Components: parameterized-trigger Created: 25/Sep/14 6:02 AM Description: Problem Currently, it is not possible to just disable a parameterized trigger, so the workaround is to either set the projects to build to disabled or to completely delete the trigger. Suggestion / Feature Request Could you add an entry to Trigger when build is to simply disable the trigger, e.g. Disabled (never triggered)? Project: Jenkins Priority: Trivial Reporter: Martin Meyer 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.
