Re: Job DSL issue create Conditional build step to send email
Please use the Job DSL mailing list (
https://groups.google.com/forum/#!forum/job-dsl-plugin) or StackOverflow (
http://stackoverflow.com/questions/tagged/jenkins-job-dsl) for Job DSL
questions.
And describe the problem in detail apart from it's not working for me
Daniel
On Wed, May 20, 2015 at 7:19 AM, Manoj Thakkar manoj.thak...@gmail.com
wrote:
Hi,
I am trying to write jobdsl to create a conditional step which will send
email if the condition is met,
It's not working for me unfortunately :( . Please help improve the code
below.
conditionalSteps {
condition {
stringsMatch('${ENV,var=RIGHT}', true, false)
}
extendedEmail(mthak...@mycopamy.com, for Componets,
Test Jira)
}
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send an
email to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/7504f06e-1cf8-4050-af0e-2d1c0f836052%40googlegroups.com
https://groups.google.com/d/msgid/jenkinsci-dev/7504f06e-1cf8-4050-af0e-2d1c0f836052%40googlegroups.com?utm_medium=emailutm_source=footer
.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/CAKqW32CNmPDr3cCmqvgy7QnJo-pbBAHDB2xh8znWxW5ZbWVC8w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: Help logging into http://scriptlerweb.appspot.com/
Hi Scott, I’m the creator of that app. It was the first implementation of a hosted catalog for scriptler, since then we created an other catalog hosted on GitHub: https://github.com/jenkinsci/jenkins-scripts/tree/master/scriptler The one on GitHub is the one which you should use for new scripts (please make sure to read the README on GH). Actually I have not looked at scritlerweb for about a year and I’m quite surprised it still has activity :) regards Domi On 19 May 2015, at 19:31, Scott Hebert sco...@gmail.com wrote: Hi, Does anyone know who runs and maintains http://scriptlerweb.appspot.com/? I have a groovy script that needs updating and it is hosted there. For some reason, I am unable to login using the Google OpenID facility. I can create a new provider, but I am unable to edit a script that was created by another provider. Barring that, I guess I can turn to hosting the script here: https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+Script+Console Thanks for your help Scott -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CALtL2uFeJoZy%3DX%2BNDRVzugVF8F3nj_%2B8PNPxbM5s4uh5rNrM5g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/68901794-E82C-4661-9CC5-F0127B00A6AE%40fortysix.ch. For more options, visit https://groups.google.com/d/optout.
Re: Uniqueness in configuration variable names
Hi, In jelly, `h.generateId()` should give you an identifier that is unique per given page rendered, though you should not rely on that in descriptor. Input name conflict between different instances of your descriptor should not be a problem as long as you are using databinding (@DataBoundConstructor and friends). How are you accessing the parameters? -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CADw-0SE7hi45Kv9WtNqxPTcZHpyRE_BL0XmL6ZQYK6isNMyZ2A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Uniqueness in configuration variable names
Hello all, I have a build step that contains a number of configuration parameters. The problem I am running into is how to distinguish which parameters belong to which build step when multiple instances of this build step are added to the same job. Is there some way to create per-instance unique names on the controls in the config.jelly? And how do you determine these names in the descriptor class? Thanks, -- Greg -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/555C6BA9.8060306%40redhat.com. For more options, visit https://groups.google.com/d/optout.
Backporting for 1.609.1 is over
Changes for next LTS are prepared, we are ready for RC. https://github.com/jenkinsci/jenkins/commits/stable-1.609 -- oliver -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/op.xyxjhlm9sbfict%40arch. For more options, visit https://groups.google.com/d/optout.
IMPORTANT: All plugins will soon require a wiki page
Hi all, Please read this if you're a *Jenkins plugin developer*, as there may be actions you need to take. **Background** As discussed recently on this list and in the community meeting last week, we would really like to raise the quality bar for Jenkins plugins. http://meetings.jenkins-ci.org/jenkins/2015/jenkins.2015-05-13-18.07.log.html#l-77 The first step is to ensure that plugins have some documentation. There are a lot of plugins out there — even brand-new ones — which have no wiki page, and therefore only show minimal information (if any!) in the Jenkins plugin manager. This makes it hard for users to find out whether the plugin is suitable, find where the source code is, who the maintainers are, how to use the plugin, what the recent changes are, for people to find plugins via Google etc etc.. It was decided that plugins which do not specify a wiki page will soon *no longer be included* in the Jenkins Update Centre (i.e. the plugin manager UI within Jenkins itself). Adding a wiki page for your plugin with an infobox and documentation is helpful for users, and it is not an unreasonable barrier to entry. Another problem is that many plugins *do* have a wiki page, but fail to specify its URL in the plugin metadata (e.g. pom.xml). This makes it hard for the code that generates the Update Centre to know what the correct wiki page is. **What will happen** * Changes to the Update Centre behaviour (in a few weeks) There is a pull request which will implement this behaviour, i.e. ignoring plugins without a valid URL when building the plugin list: https://github.com/jenkinsci/backend-update-center2/pull/20 This should be merged at some point in June, i.e. in a few weeks. Exactly when will likely be discussed in the next community meeting. * Transition period (several months) Because this change will affect ~10% of all current plugin releases, there will be a transitional phase, where plugins that don't specify a wiki page will still be included in the Update Centre. This happens via the wiki overrides mechanism of the Update Centre: https://github.com/jenkinsci/backend-update-center2/blob/beb31db/src/main/resources/wiki-overrides.properties Any plugin on that list will remain in the Update Centre until the final cut-off. Plugins which have *no* wiki page whatsoever may be temporarily pointed to a Plugin Page Missing wiki page, explaining to users that the maintainer has not documented their plugin, and that they should be encouraged to do so. Such plugins will therefore also remain in the Update Centre during this period. * Final cut off After the transitional period, the temporary wiki overrides list will be cleared out, and any plugins that still do not specify a wiki page will no longer be listed in the Update Centre. **Action required by plugin developers:** 1. Check whether your plugin is on either of these two lists: Plugins which *do not* have a wiki page: https://gist.github.com/orrc/4c149b62c62362191972 Plugins which have a wiki page, but *do not* list it in the metadata: https://github.com/jenkinsci/backend-update-center2/blob/beb31db/src/main/resources/wiki-overrides.properties 2. If your plugin is not on either list, there's nothing to do! :) 3. If your plugin is listed here, ensure you have a wiki page: https://wiki.jenkins-ci.org/x/AgAcAQ#HostingPlugins-CreatingaWikipage 4. Ensure that the correct wiki URL is listed in your plugin metadata: https://wiki.jenkins-ci.org/x/AgAcAQ#HostingPlugins-AddingyourWikipagetoyourrepo Examples of how to specify this for various plugin build systems: Maven: https://github.com/jenkinsci/git-tag-message-plugin/blob/master/pom.xml#L15 Gradle: https://github.com/jenkinsci/job-dsl-plugin/blob/31216b7/job-dsl-plugin/build.gradle#L23 Ruby: https://github.com/jenkinsci/pathignore-plugin/blob/22412e7/pathignore.pluginspec#L7 4a. While you're there, please also make sure that your scm info is present and pointing to your jenkinsci repository, as future Update Centre changes may enforce this more strictly: https://wiki.jenkins-ci.org/x/AgAcAQ#HostingPlugins-DeclareyourrepositoryinyourPOM 5. Create a new plugin release (some time before the final cut off) Please check the above lists, and make the required changes as soon as possible. Pass on the word if you know any of the maintainers on those lists. Feel free also to submit pull requests to the plugins on the wiki overrides list! Thanks for reading this far, and let me know if you have any questions :) Thanks, Chris -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/555D16FA.8040808%40orr.me.uk. For more options, visit
RE: Request for Commit Access to SSH-Plugin
I hate to bump this, but I did not want to start a new thread. I have tried getting onto IRC, but I think I am missing the peak times as I have not managed to get a response yet. Can somebody please help me with this? Thank You, John Tatum john.ta...@live.com http://scientifichooliganism.net Although this e-mail and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and/or upon which it is opened, it is the responsibility of the recipient(s) to ensure that it is virus and/or defect free and John Tatum bears no responsibility for any loss and/or damage arising in any way from its use. From: john.ta...@live.com To: jenkinsci-dev@googlegroups.com Subject: Request for Commit Access to SSH-Plugin Date: Sat, 16 May 2015 13:51:55 -0400 May I have commit access for the SSH-Plugin, specifically https://github.com/jenkinsci/ssh-plugin? My GitHub user ID is johnny-b-goode. I have tried reaching out to the maintainer indicated on the wiki, Edmund Wagner, but have not received a response. His last commit was about nine months ago. There are currently three pull requests pending, and a number of issues in Jira that should be fairly quick fixes. Thank You, John Tatum john.ta...@live.com http://scientifichooliganism.net Although this e-mail and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and/or upon which it is opened, it is the responsibility of the recipient(s) to ensure that it is virus and/or defect free and John Tatum bears no responsibility for any loss and/or damage arising in any way from its use. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/BLU179-W958A2F29DE33C82A692677F7C60%40phx.gbl. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/BLU179-W71BA62183D5EF59F238159F7C10%40phx.gbl. For more options, visit https://groups.google.com/d/optout.
Re: Backporting for 1.609.1 is over
Binaries posted: http://mirrors.jenkins-ci.org/ 2015-05-20 5:50 GMT-07:00 oliver gondža ogon...@gmail.com: Changes for next LTS are prepared, we are ready for RC. https://github.com/jenkinsci/jenkins/commits/stable-1.609 -- oliver -- Kohsuke Kawaguchi -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4xYjehapT_T8vB7ADxgMhm_jPfBOzBbb%3D7HspN-nCd1-g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
