[JIRA] (JENKINS-61167) Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error
Title: Message Title Andrew Sumner commented on JENKINS-61167 Re: Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error It shouldn't be an issue with the .7z extension as this is packed into a universal package before being uploaded to proget, however I will do some testing to rule that out. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204701.1582203816000.6801.1582699920145%40Atlassian.JIRA.
[JIRA] (JENKINS-61167) Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error
Title: Message Title Andrew Sumner commented on JENKINS-61167 Re: Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error I don't think that is the problem - that is quite an old issue and I'm able to upload 200MB files to my ProGet instance. There is an issue with this plugin (rather than proget) around file size but I thought that was well in excess of 58 MB and throws an out of memory exceptions rather than Bad Gateway. I've been meaning to fix this for a while so will look for a solution. Seems to be an issue running under Jenkins as the code doesn't have this problem when run as a unit test. If you can't wait for this there is a [command line tool|https://docs.inedo.com/docs/upack/tools-and-libraries/upack-cli] for ProGet that you could use instead of this plugin. Obviously not as handy but would get your pipeline running while I work on the plugin. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204701.1582203816000.6627.1582664820280%40Atlassian.JIRA.
[JIRA] (JENKINS-60613) Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0
Title: Message Title Andrew Sumner commented on JENKINS-60613 Re: Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0 Just to let you know - I haven't forgotten about this. I am in the process of moving house so I haven't had much spare time lately. This change is ready to go. However... the BuildMaster 6.2.5 release has a bug in one of the APIs used by the "wait for build to complete" option. There where a couple of other minor changes to the API but those were easily fixed. As soon as I have a fix for this I will be getting a new version out. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203842.1577724088000.6620.1582663800115%40Atlassian.JIRA.
[JIRA] (JENKINS-61167) Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error
Title: Message Title
Andrew Sumner edited a comment on JENKINS-61167
Re: Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error
I haven't been able to duplicate this issue on my setup - the best I have come up with is to get a 400 level errors when I put in invalid parameters for ProGet.Can you create a new pipeline with the following code (you may need to tweak some values) as this works for me, I just want to understand if it's a problem with what you are sending or an access issue. {{ pipeline { agent any }}{{ stages { stage('Main') { steps { bat '''DEL *.TXT /Q if not exist "subfolder" mkdir subfolder DEL *.upack /Q ECHO Build Tag: %BUILD_TAG% > subfolder/Example.txt''' script { VERSION = "1.1.${BUILD_NUMBER}" } echo "version = '${VERSION}'" uploadProgetPackage artifacts: 'subfolder/Example.txt', feedName: 'Example1', groupName: 'jenkins/pipleline', packageName: 'JenkinsPackage', version: "${VERSION}" } } }} }} {color:#172b4d}Sorry I don't have a better answer for you, however I'm sure we can get to the bottom of this.{color}{color:#172b4d}Is there anything else you can tell me about your setup - ProGet or the Jenkins build? eg: {color} # {color:#172b4d}I assume they are on the same network - no firewalls in they way{color} # {color:#172b4d}Is the jenkins job running on an agent or on the Jenkins master node{color} # ?
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google
[JIRA] (JENKINS-61167) Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error
Title: Message Title
Andrew Sumner edited a comment on JENKINS-61167
Re: Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error
I haven't been able to duplicate this issue on my setup - the best I have come up with is to get a 400 level errors when I put in invalid parameters for ProGet.Can you create a new pipeline with the following code (you may need to tweak some values) as this works for me, I just want to understand if it's a problem with what you are sending or an access issue. {{pipeline { agent any}}{{ stages { stage('Main') { steps { bat '''DEL *.TXT /Q if not exist "subfolder" mkdir subfolder DEL *.upack /Q ECHO Build Tag: %BUILD_TAG% > subfolder/Example.txt''' script { VERSION = "1.1.${BUILD_NUMBER}" } echo "version = '${VERSION}'" uploadProgetPackage artifacts: 'subfolder/Example.txt', feedName: ' Example Example1 ', groupName: 'jenkins/pipleline', packageName: 'JenkinsPackage', version: "${VERSION}" } } {color:#172b4d}Sorry I don't have a better answer for you, however I'm sure we can get to the bottom of this.{color}{color:#172b4d}Is there anything else you can tell me about your setup - ProGet or the Jenkins build? eg: {color} # {color:#172b4d}I assume they are on the same network - no firewalls in they way{color} # {color:#172b4d}Is the jenkins job running on an agent or on the Jenkins master node{color} # ?
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the
[JIRA] (JENKINS-61167) Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error
Title: Message Title
Andrew Sumner commented on JENKINS-61167
Re: Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error
I haven't been able to duplicate this issue on my setup - the best I have come up with is to get a 400 level errors when I put in invalid parameters for ProGet. Can you create a new pipeline with the following code (you may need to tweak some values) as this works for me, I just want to understand if it's a problem with what you are sending or an access issue. {{pipeline { agent any}}{{ stages { stage('Main') { steps { bat '''DEL *.TXT /Q if not exist "subfolder" mkdir subfolder DEL *.upack /Q ECHO Build Tag: %BUILD_TAG% > subfolder/Example.txt''' script { VERSION = "1.1.${BUILD_NUMBER}" } echo "version = '${VERSION}'" uploadProgetPackage artifacts: 'subfolder/Example.txt', feedName: 'Example', groupName: 'jenkins/pipleline', packageName: 'JenkinsPackage', version: "${VERSION}" } } } } }} Sorry I don't have a better answer for you, however I'm sure we can get to the bottom of this. Is there anything else you can tell me about your setup - ProGet or the Jenkins build? eg:
I assume they are on the same network - no firewalls in they way
Is the jenkins job running on an agent or on the Jenkins master node
?
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-61167) Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error
Title: Message Title Andrew Sumner edited a comment on JENKINS-61167 Re: Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error I will have a look at this over the weekend and get back to you as soon as I can. Could you let me know the version of both the jenkins proget plugin and proget application that versions you are using ? for the following: * Jenkins * Jenkins ProGet Plugin * ProGet application I know there is an issue with large files (over 200MB) that I'm hoping to look into soon, however I don't think this would explain your issue. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204701.1582203816000.4024.1582241220129%40Atlassian.JIRA.
[JIRA] (JENKINS-61167) Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error
Title: Message Title Andrew Sumner commented on JENKINS-61167 Re: Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error I will have a look at this over the weekend and get back to you as soon as I can. Could you let me know the version of both the jenkins proget plugin and proget application that you are using? I know there is an issue with large files (over 200MB) that I'm hoping to look into soon, however I don't think this would explain your issue. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204701.1582203816000.4022.1582241040207%40Atlassian.JIRA.
[JIRA] (JENKINS-60613) Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0
Title: Message Title Andrew Sumner commented on JENKINS-60613 Re: Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0 I've got this working with seperate parameters and even support builds as well as application and release. I've got this sitting in a seperate branch and I'm not planning on releasing it for the moment unless anyone asks for it, so if you ever want to move in that direction let me know Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203842.1577724088000.5915.1579921920155%40Atlassian.JIRA.
[JIRA] (JENKINS-60613) Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0
Title: Message Title Andrew Sumner commented on JENKINS-60613 Re: Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0 I've released version 3.1 to support this. Let me know how it goes. As a first cut the cascading dropdown was easier to implement as a single parameter with two dropdowns, so let me know how this goes - and whether you need a build number dropdown as well. I would still like to seperate this out into seperate parameters and get a similar behviour to active choices so depending on time constraints I will continue to play with this. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203842.1577724088000.6812.1578824220151%40Atlassian.JIRA.
[JIRA] (JENKINS-60613) Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0
Title: Message Title Andrew Sumner commented on JENKINS-60613 Re: Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0 Good news, I've finally got this working. The solution ended up being rather simple - around 20 lines of code. Shame the Jenkins documentation is garbage, it should have been much easier to get this up and running. I've got a bit more testing to do but should have a new release out in the next few days. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203842.1577724088000.4761.1578491400131%40Atlassian.JIRA.
[JIRA] (JENKINS-60613) Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0
Title: Message Title Andrew Sumner commented on JENKINS-60613 Re: Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0 I haven't given up yet, there is one more thing I want to try . Scriptler is an optional component, it can all be done within the active choice plugin. Scriptler was just a little tidier which is why I documented that approach. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203842.1577724088000.3215.1578359700125%40Atlassian.JIRA.
[JIRA] (JENKINS-60613) Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0
Title: Message Title Andrew Sumner commented on JENKINS-60613 Re: Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0 Let me know how this works for you. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203842.1577724088000.2257.1578186180127%40Atlassian.JIRA.
[JIRA] (JENKINS-60613) Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0
Title: Message Title Andrew Sumner commented on JENKINS-60613 Re: Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0 Adding reactive parameters turned out to be a LOT harder than I anticipated, so I've taken a different tack and used the [active choices plugin|https://plugins.jenkins.io/uno-choice.] I've documented this in the attached word document. You can either store the groovy code using the [scriptler|https://plugins.jenkins.io/scriptler []|https://plugins.jenkins.io/uno-choice].] plugin, or directly in the job with the active choice plugin. Select Application and Release.docx Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203842.1577724088000.2255.1578186120286%40Atlassian.JIRA.
[JIRA] (JENKINS-60613) Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0
Title: Message Title Andrew Sumner updated an issue Jenkins / JENKINS-60613 Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0 Change By: Andrew Sumner Attachment: Select Application and Release.docx Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203842.1577724088000.2253.1578185940159%40Atlassian.JIRA.
[JIRA] (JENKINS-60613) Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0
Title: Message Title Andrew Sumner commented on JENKINS-60613 Re: Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0 Just to make sure I'm heading down the right track: You would like the BM Release Parameter to have the option of selecting both the app and release at build time. This should be doable. Does this solve the "env vars as build params" from the first paragraph, or do you mean you still need the ability to to enter a custom variable into the task config's app & release options instead of just the options I have provided in the list? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203842.1577724088000.1274.1577836020205%40Atlassian.JIRA.
[JIRA] (JENKINS-60613) Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0
Title: Message Title Andrew Sumner commented on JENKINS-60613 Re: Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0 Updated wiki is at https://plugins.jenkins.io/inedo-buildmaster, this describes the release parameter, changes to variable names, etc. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203842.1577724088000.1146.1577768520129%40Atlassian.JIRA.
[JIRA] (JENKINS-60613) Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0
Title: Message Title Andrew Sumner commented on JENKINS-60613 Re: Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0 Let me know how it goes. If it’s going to be easier for you I’m happy to get a patch out, otherwise I’ll leave it as is for now. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203842.1577724088000.1144.1577768222830%40Atlassian.JIRA.
[JIRA] (JENKINS-60613) Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0
Title: Message Title Andrew Sumner commented on JENKINS-60613 Re: Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0 Ah, you're correct - I haven't catered for custom variables. I was assuming that people would just use the ones injected from the environment or parameter tasks. I had a quick look at using the combobox jelly tag instead of the select option, I don't like how this behaves so will take a little longer to get this working how I would like it - eta a couple of days. What is the source for the variable that holds the release number? There might be a way I can better support your use case. For example the plugin now supports a BuildMaster Parameter task that allows you to select a release a build time. Alternatively you could ignore the environment task altogether and inject your own variables: "BUILDMASTER_APPLICATION_ID" - can contain either the id or application name "BUILDMASTER_RELEASE_NUMBER" - set that to the desired release number Ignoring this issue, are there any other features you'd like to see in this plugin? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web
[JIRA] (JENKINS-59401) After Upgrade to Inedo Plugin 2.5.0 could not create package
Title: Message Title Andrew Sumner closed an issue as Fixed Jenkins / JENKINS-59401 After Upgrade to Inedo Plugin 2.5.0 could not create package Change By: Andrew Sumner Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201958.1568681322000.15316.1577169480515%40Atlassian.JIRA.
[JIRA] (JENKINS-59401) After Upgrade to Inedo Plugin 2.5.0 could not create package
Title: Message Title Andrew Sumner resolved as Fixed This is fixed by release 3.0.0 - unfortunately this is a breaking release. I've been doing some work to align the BuildMaster Jenkins Extension and the Jenkins BuildMaster Plugin and took the opportunity to finish of change back from package to build api and rename all parameters and exported variables. Jenkins / JENKINS-59401 After Upgrade to Inedo Plugin 2.5.0 could not create package Change By: Andrew Sumner Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received
[JIRA] (JENKINS-59373) JenkinsRule not working with Gradle JPI Plugin
Title: Message Title Andrew Sumner closed an issue as Fixed I tried again after rebooting PC and running via gradle and then eclipse, it worked fine. Thanks and sorry for wasting your time. Jenkins / JENKINS-59373 JenkinsRule not working with Gradle JPI Plugin Change By: Andrew Sumner Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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
[JIRA] (JENKINS-59401) After Upgrade to Inedo Plugin 2.5.0 could not create package
Title: Message Title Andrew Sumner commented on JENKINS-59401 Re: After Upgrade to Inedo Plugin 2.5.0 could not create package Odd, should have been a fairly minor change, I did upgrade some dependencies. Will take me a few days to get to it as my server running BuildMaster has had a melt down Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201958.1568681322000.247.1568802480792%40Atlassian.JIRA.
[JIRA] (JENKINS-59373) JenkinsRule not working with Gradle JPI Plugin
Title: Message Title
Andrew Sumner commented on JENKINS-59373
Re: JenkinsRule not working with Gradle JPI Plugin
That changelong leads to https://groups.google.com/forum/#!topic/job-dsl-plugin/oPjqGR6VTpU and https://github.com/jenkinsci/job-dsl-plugin/blob/ca99792f54e2f3a754e70a9a69e3c5f36c885db3/docs/Testing-DSL-Scripts.md which indicate that this can be fixed by adding testCompile "org.jenkins-ci.main:jenkins-war:${jenkinsVersion}". I've tried this and it makes no difference: https://github.com/jenkinsci/inedo-proget-plugin/blob/master/build.gradle
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201926.1568434262000.4022.1568619720138%40Atlassian.JIRA.
[JIRA] (JENKINS-59373) JenkinsRule not working with Gradle JPI Plugin
Title: Message Title Andrew Sumner created an issue Jenkins / JENKINS-59373 JenkinsRule not working with Gradle JPI Plugin Issue Type: Bug Assignee: Steve Hill Components: gradle-jpi-plugin Created: 2019-09-14 04:11 Priority: Major Reporter: Andrew Sumner I'm updating the jenkinsVersion I rely on in my project https://github.com/jenkinsci/inedo-proget-plugin/tree/SecretManagement but are having problems with tests that use JenkinsRule. Up to jenkins version 2.63 it works fine, from 2.64 onwards I get: java.lang.AssertionError: D:\Work\gradle_user_home\caches\modules-2\files-2.1\org.jenkins-ci.main\jenkins-core\2.64\6766ac4d8dd4a6ca1920f5156bb10be656d4ded3\jenkins-core-2.64.jar is not in the expected location, and jenkins-war-*.war was not in D:\Work\Eclipse\workspace\inedo-proget-plugin\bin\main; D:\Work\Eclipse\workspace\inedo-proget-plugin\bin\test; D:\Work\gradle_user_home\caches\modules-2\files-2.1\org.concordion\cubano-httpeasy\0.3.5\f25d55eb0bc86ff10524bf91fa209be0e305ffb4\cubano-httpeasy-0.3.5.jar; ... long list of jar files ... D:\Work\Eclipse\eclipse-oxygen\eclipse\configuration\org.eclipse.osgi\413\0\.cp; D:\Work\Eclipse\eclipse-oxygen\eclipse\configuration\org.eclipse.osgi\1168\0\.cp at org.jvnet.hudson.test.WarExploder.explode(WarExploder.java:119) at org.jvnet.hudson.test.WarExploder.(WarExploder.java:68) at org.jvnet.hudson.test.JenkinsRule._createWebServer(JenkinsRule.java:748) at org.jvnet.hudson.test.JenkinsRule.createWebServer(JenkinsRule.java:718) at org.jvnet.hudson.test.JenkinsRule.newHudson(JenkinsRule.java:670) at org.jvnet.hudson.test.JenkinsRule.before(JenkinsRule.java:402) at org.jvnet.hudson.test.JenkinsRule$1.evaluate(JenkinsRule.java:595) at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298) at
[JIRA] (JENKINS-50976) At end of build plugin is querying BuildMaster for apps deployable info
Title: Message Title Andrew Sumner resolved as Fixed Jenkins / JENKINS-50976 At end of build plugin is querying BuildMaster for apps deployable info Change By: Andrew Sumner Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-50976) At end of build plugin is querying BuildMaster for apps deployable info
Title: Message Title Andrew Sumner started work on JENKINS-50976 Change By: Andrew Sumner Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-50976) At end of build plugin is querying BuildMaster for apps deployable info
Title: Message Title Andrew Sumner closed an issue as Fixed Jenkins / JENKINS-50976 At end of build plugin is querying BuildMaster for apps deployable info Change By: Andrew Sumner Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-36730) Need to allow full sem versions like Nuget
Title: Message Title Andrew Sumner resolved as Fixed Jenkins / JENKINS-36730 Need to allow full sem versions like Nuget Change By: Andrew Sumner Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-36730) Need to allow full sem versions like Nuget
Title: Message Title Andrew Sumner commented on JENKINS-36730 Re: Need to allow full sem versions like Nuget Just released version 1.1 of the pugin to support this. The plugin no longer does any validation of the version number, but relies on ProGet to return an error if the version format is incorrect. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-36730) Need to allow full sem versions like Nuget
Title: Message Title Andrew Sumner closed an issue as Fixed Jenkins / JENKINS-36730 Need to allow full sem versions like Nuget Change By: Andrew Sumner Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-37193) inedo-buildmaster-plugin is Not compatible with BuildMaster 5.x
Title: Message Title Andrew Sumner closed an issue as Fixed Jenkins / JENKINS-37193 inedo-buildmaster-plugin is Not compatible with BuildMaster 5.x Change By: Andrew Sumner Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-38633) As a user I want to be able to start a specific stage of a BuildMaster Deployment pipeline.
Title: Message Title Andrew Sumner closed an issue as Fixed Jenkins / JENKINS-38633 As a user I want to be able to start a specific stage of a BuildMaster Deployment pipeline. Change By: Andrew Sumner Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-42036) As a User I want to be able to pass variables when using the Deploy to Stage function
Title: Message Title Andrew Sumner closed an issue as Fixed Jenkins / JENKINS-42036 As a User I want to be able to pass variables when using the Deploy to Stage function Change By: Andrew Sumner Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-45578) As a user I want to be able to deploy to a stage even if that stage has deployed before
Title: Message Title Andrew Sumner closed an issue as Fixed Jenkins / JENKINS-45578 As a user I want to be able to deploy to a stage even if that stage has deployed before Change By: Andrew Sumner Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-45498) During Plugin Execution log shows ProGet not BuildMaster
Title: Message Title Andrew Sumner closed an issue as Fixed Jenkins / JENKINS-45498 During Plugin Execution log shows ProGet not BuildMaster Change By: Andrew Sumner Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-50976) At end of build plugin is querying BuildMaster for apps deployable info
Title: Message Title Andrew Sumner commented on JENKINS-50976 Re: At end of build plugin is querying BuildMaster for apps deployable info Is this still happening or can the issue be closed? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-53336) inedo-buildmaster - trigger deployment always returns that job was aborted if job had warnings on BuildMaster
Title: Message Title Andrew Sumner closed an issue as Fixed Jenkins / JENKINS-53336 inedo-buildmaster - trigger deployment always returns that job was aborted if job had warnings on BuildMaster Change By: Andrew Sumner Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-53263) indeo-buildmaster Create Package not passing variables
Title: Message Title Andrew Sumner closed an issue as Fixed Jenkins / JENKINS-53263 indeo-buildmaster Create Package not passing variables Change By: Andrew Sumner Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-54286) Unable to use variable tokens as build property values in Create Package in Declarative Script
Title: Message Title Andrew Sumner resolved as Fixed Jenkins / JENKINS-54286 Unable to use variable tokens as build property values in Create Package in Declarative Script Change By: Andrew Sumner Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-54286) Unable to use variable tokens as build property values in Create Package in Declarative Script
Title: Message Title Andrew Sumner closed an issue as Fixed Jenkins / JENKINS-54286 Unable to use variable tokens as build property values in Create Package in Declarative Script Change By: Andrew Sumner Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-53336) inedo-buildmaster - trigger deployment always returns that job was aborted if job had warnings on BuildMaster
Title: Message Title Andrew Sumner resolved as Fixed Jenkins / JENKINS-53336 inedo-buildmaster - trigger deployment always returns that job was aborted if job had warnings on BuildMaster Change By: Andrew Sumner Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-54286) Unable to use variable tokens as build property values in Create Package in Declarative Script
Title: Message Title
Andrew Sumner edited a comment on JENKINS-54286
Re: Unable to use variable tokens as build property values in Create Package in Declarative Script
Not sure what's going on here. I've created a sample deployment using jenkins buildmaster plugin 2.1.1. Can you: # Confirm which version of the plugin you are using. Ideally you'll need to upgrade to 2.1.1 if you're not already using this. Note that this version has renamed {color:#172b4d}setBuildVariables{color} from buildMasterCreatePackage to packageVariables. # Echo out your {color:#009100}gitprops{color} variable and ensure it is populated correctly # Show how {color:#009100}gitprops{color} is being populated {color:#172b4d}I've created a sample deployment using jenkins buildmaster plugin 2.1.1 to attempt to duplicate your issue. {color} As you can see in the log output below that the two variables (commit and fred) appear in the logs, but I cannot see the same for your output. All I can think is that you're using an early release of the plugin that contains a bug or that somehow the variables not not getting passed to the plugin correctly. Code:{code:java}node {scmVars = git(credentialsId: 'andrew-git', url: 'https://github.com/andrew-sumner/Accounts.git')echo "$scmVars"buildMasterWithApplicationRelease(applicationId: '2', packageNumberSource: 'BUILDMASTER') {BUILDMASTER_PACKAGE_NUMBER = buildMasterCreatePackage(applicationId: BUILDMASTER_APPLICATION_ID, releaseNumber: BUILDMASTER_RELEASE_NUMBER, packageNumber: BUILDMASTER_PACKAGE_NUMBER, deployToFirstStage: true, waitTillBuildCompleted: [printLogOnFailure: true], packageVariables: [preserveVariables: false, variables: "fred=one\ncommit=${scmVars.GIT_COMMIT}"])}}{code}Log: {code:java}[Pipeline] echo (hide)[GIT_BRANCH:origin/master, GIT_COMMIT:b9f3e9741ea20e767ddbc7d6087ba7afc09221e7, GIT_LOCAL_BRANCH:master, GIT_PREVIOUS_COMMIT:b9f3e9741ea20e767ddbc7d6087ba7afc09221e7, GIT_PREVIOUS_SUCCESSFUL_COMMIT:b9f3e9741ea20e767ddbc7d6087ba7afc09221e7, GIT_URL:https://github.com/andrew-sumner/Accounts.git][Pipeline] buildMasterWithApplicationRelease (hide)[BuildMaster] Sending POST to http://inedo:8622/api/releases[BuildMaster] With application/x-www-form-urlencoded content:[BuildMaster] key=xxx=2=active[BuildMaster] Sending POST to http://inedo:8622/api/releases[BuildMaster] With application/x-www-form-urlencoded content:[BuildMaster] key=xxx=2=0.0.0[BuildMaster] Inject environment variable BUILDMASTER_APPLICATION_ID=2[BuildMaster] Inject environment variable BUILDMASTER_RELEASE_NUMBER=0.0.0[BuildMaster] Inject environment variable BUILDMASTER_PACKAGE_NUMBER=9, sourced from BuildMaster[Pipeline] { (hide)[Pipeline] buildMasterCreatePackage (hide)[BuildMaster] Sending GET to http://inedo:8622/api/json/Applications_GetApplication?API_Key=xxx_Id=2[BuildMaster] Create BuildMaster package with PackageNumber=9[BuildMaster] Sending PUT to http://inedo:8622/api/releases/packages/create[BuildMaster] With application/x-www-form-urlencoded content:[BuildMaster] key=xxx=2=0.0.0=9&$commit=b9f3e9741ea20e767ddbc7d6087ba7afc09221e7&$fred=one[BuildMaster] Wait for any active deployments to complete{code}{color:#33} {color}
[JIRA] (JENKINS-54286) Unable to use variable tokens as build property values in Create Package in Declarative Script
Title: Message Title
Andrew Sumner commented on JENKINS-54286
Re: Unable to use variable tokens as build property values in Create Package in Declarative Script
Not sure what's going on here. I've created a sample deployment using jenkins buildmaster plugin 2.1.1. Can you:
Confirm which version of the plugin you are using. Ideally you'll need to upgrade to 2.1.1 if you're not already using this. Note that this version has renamed setBuildVariables from buildMasterCreatePackage to packageVariables.
Echo out your gitprops variable and ensure it is populated correctly
Show how gitprops is being populated
As you can see in the log output below that the two variables (commit and fred) appear in the logs, but I cannot see the same for your output. All I can think is that you're using an early release of the plugin that contains a bug or that somehow the variables not not getting passed to the plugin correctly. Code:
node {
scmVars = git(credentialsId: 'andrew-git', url: 'https://github.com/andrew-sumner/Accounts.git')
echo "$scmVars"
buildMasterWithApplicationRelease(applicationId: '2', packageNumberSource: 'BUILDMASTER') {
BUILDMASTER_PACKAGE_NUMBER = buildMasterCreatePackage(applicationId: BUILDMASTER_APPLICATION_ID, releaseNumber: BUILDMASTER_RELEASE_NUMBER, packageNumber: BUILDMASTER_PACKAGE_NUMBER, deployToFirstStage: true, waitTillBuildCompleted: [printLogOnFailure: true], packageVariables: [preserveVariables: false, variables: "fred=one\ncommit=${scmVars.GIT_COMMIT}"])
}
}
Log:
[Pipeline] echo (hide)
[GIT_BRANCH:origin/master, GIT_COMMIT:b9f3e9741ea20e767ddbc7d6087ba7afc09221e7, GIT_LOCAL_BRANCH:master, GIT_PREVIOUS_COMMIT:b9f3e9741ea20e767ddbc7d6087ba7afc09221e7, GIT_PREVIOUS_SUCCESSFUL_COMMIT:b9f3e9741ea20e767ddbc7d6087ba7afc09221e7, GIT_URL:https://github.com/andrew-sumner/Accounts.git]
[Pipeline] buildMasterWithApplicationRelease (hide)
[BuildMaster] Sending POST to http://inedo:8622/api/releases
[BuildMaster] With application/x-www-form-urlencoded content:
[BuildMaster] key=xxx=2=active
[BuildMaster] Sending POST to http://inedo:8622/api/releases
[BuildMaster] With application/x-www-form-urlencoded content:
[BuildMaster] key=xxx=2=0.0.0
[BuildMaster] Inject environment variable BUILDMASTER_APPLICATION_ID=2
[BuildMaster] Inject environment variable BUILDMASTER_RELEASE_NUMBER=0.0.0
[BuildMaster] Inject environment variable BUILDMASTER_PACKAGE_NUMBER=9, sourced from BuildMaster
[Pipeline] { (hide)
[Pipeline] buildMasterCreatePackage (hide)
[BuildMaster] Sending GET to http://inedo:8622/api/json/Applications_GetApplication?API_Key=xxx_Id=2
[BuildMaster] Create BuildMaster package with PackageNumber=9
[BuildMaster] Sending PUT to http://inedo:8622/api/releases/packages/create
[BuildMaster] With application/x-www-form-urlencoded content:
[BuildMaster]
[JIRA] (JENKINS-54286) Unable to use variable tokens as build property values in Create Package in Declarative Script
Title: Message Title
Andrew Sumner commented on JENKINS-54286
Re: Unable to use variable tokens as build property values in Create Package in Declarative Script
$gitprops.GitVersion_FullSemVer probably needs to be ${$gitprops.GitVersion_FullSemVer} Can you turn on API logging in buildmaster section of Jenkins configuration page and reply back with the log output? How are you setting ${env.BuildMaster_appId}" and "${env.BuildMaster_deployableId}" I'm also concerned that the Jenkins job is succeeding when buildmaster is failing. That definitely should not happen. I'll try to replicate that tonight.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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] (JENKINS-54286) Unable to use variable tokens as build property values in Create Package in Declarative Script
Title: Message Title Andrew Sumner commented on JENKINS-54286 Re: Unable to use variable tokens as build property values in Create Package in Declarative Script Unfortunately I could not find any way of updating the settings and had to change the format to support pipeline script. My only suggestion is editing the Jenkins job xml definition and manually to get it into the correct format. Not ideal I know. I'll try updating the compatibleSinceVersion property (it's currently set to 1.7, but should be 2.0) which might display a warning message for the upgrade. There is a warning on the Wiki but it is very easily overlooked. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-54286) Unable to use variable tokens as build property values in Create Package in Declarative Script
Title: Message Title
Andrew Sumner edited a comment on JENKINS-54286
Re: Unable to use variable tokens as build property values in Create Package in Declarative Script
I've released a new version as I didn't like the syntax for adding variables to a package - you'll need to install version 2.1.1 of the plugin.Syntax should be: {{ ... = buildMasterCreatePackage(..., packageVariables: [ }}{{ variables: }}{{ "hello=world\nsource=$BUILD_URL" }}{{ ]) }} {{Let me know how that goes. If this is not what you're after can you provide an example of what you're doing thanks.}}Also: I've just upgraded to BuildMaster 6.0.11 and there has been a change in the security model which is preventing access to the APIs - so this is just a friendly hint not to upgrade BuildMaster just yet :) {{ }}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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] (JENKINS-54286) Unable to use variable tokens as build property values in Create Package in Declarative Script
Title: Message Title
Andrew Sumner commented on JENKINS-54286
Re: Unable to use variable tokens as build property values in Create Package in Declarative Script
I've released a new version as I didn't like the syntax for adding variables to a package - you'll need to install version 2.1.1 of the plugin. Syntax should be: ... = buildMasterCreatePackage(..., packageVariables: [}}{{variables: }}{{"hello=world\nsource=$BUILD_URL"}}{{]) Let me know how that goes. If this is not what you're after can you provide an example of what you're doing thanks. Also: I've just upgraded to BuildMaster 6.0.11 and there has been a change in the security model which is preventing access to the APIs - so this is just a friendly hint not to upgrade BuildMaster just yet
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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] (JENKINS-53336) inedo-buildmaster - trigger deployment always returns that job was aborted if job had warnings on BuildMaster
Title: Message Title Andrew Sumner commented on JENKINS-53336 Re: inedo-buildmaster - trigger deployment always returns that job was aborted if job had warnings on BuildMaster Do you have any need to mark the job in jenkins as having warnings? I had a quick look and cannot see an obvious way to do this so it would require some further investigation. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-53336) inedo-buildmaster - trigger deployment always returns that job was aborted if job had warnings on BuildMaster
Title: Message Title
Andrew Sumner edited a comment on JENKINS-53336
Re: inedo-buildmaster - trigger deployment always returns that job was aborted if job had warnings on BuildMaster
I've updated to treat the {color:#172b4d}"warned"{color} status returned from "create package" and "deploy to stage" as successful. This is being released as version 2.0.2.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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] (JENKINS-53336) inedo-buildmaster - trigger deployment always returns that job was aborted if job had warnings on BuildMaster
Title: Message Title Andrew Sumner commented on JENKINS-53336 Re: inedo-buildmaster - trigger deployment always returns that job was aborted if job had warnings on BuildMaster I've updated to treat the "warned" status returned from "create package" and "deploy to stage" as successful. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-53336) inedo-buildmaster - trigger deployment always returns that job was aborted if job had warnings on BuildMaster
Title: Message Title Andrew Sumner commented on JENKINS-53336 Re: inedo-buildmaster - trigger deployment always returns that job was aborted if job had warnings on BuildMaster I’ll try to look at this tonight, but more likely to be the weekend. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-53263) indeo-buildmaster Create Package not passing variables
Title: Message Title Andrew Sumner edited a comment on JENKINS-53263 Re: indeo-buildmaster Create Package not passing variables This has been published as version 2.0.1, it may take an hour or two for it to become available. Boiled down to an if statement in the wrong place :( Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-53263) indeo-buildmaster Create Package not passing variables
Title: Message Title Andrew Sumner commented on JENKINS-53263 Re: indeo-buildmaster Create Package not passing variables This has been published as version 2.0.1, it may take an hour or two for it to become available. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-53263) indeo-buildmaster Create Package not passing variables
Title: Message Title Andrew Sumner resolved as Fixed Jenkins / JENKINS-53263 indeo-buildmaster Create Package not passing variables Change By: Andrew Sumner Status: Open Resolved Resolution: Fixed Released As: Version 2.0.1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-53263) indeo-buildmaster Create Package not passing variables
Title: Message Title Andrew Sumner commented on JENKINS-53263 Re: indeo-buildmaster Create Package not passing variables Hmm, will look into this tonight. Thanks for the report. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-42036) As a User I want to be able to pass variables when using the Deploy to Stage function
Title: Message Title Andrew Sumner commented on JENKINS-42036 Re: As a User I want to be able to pass variables when using the Deploy to Stage function I'm currently trying to get this plugin to work with pipeline script, so I'd make this next on the list Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-37194) Allow Tokens via Token Macro plugin
Title: Message Title Andrew Sumner commented on JENKINS-37194 Re: Allow Tokens via Token Macro plugin I'll have to look into this one, I've not used that plugin before. Always happy to accept a pull request though Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-38633) As a user I want to be able to start a specific stage of a BuildMaster Deployment pipeline.
Title: Message Title Andrew Sumner edited a comment on JENKINS-38633 Re: As a user I want to be able to start a specific stage of a BuildMaster Deployment pipeline. I've released another version (1.6) which aligns the code with the proget plugin and fixes an issue I found with some requests being cached when running on a slave - probably only affected the proget plugin but I figured it was worth patching this one as well. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-38633) As a user I want to be able to start a specific stage of a BuildMaster Deployment pipeline.
Title: Message Title Andrew Sumner edited a comment on JENKINS-38633 Re: As a user I want to be able to start a specific stage of a BuildMaster Deployment pipeline. I've released another version which aligns the code with the proget plugin and fixes an issue I found with some requests being cached when running on a slave - probably only affected the proget plugin but I figured it was worth patching this one as well. Also, following up on your comments on the wiki page: _"Could you add Token support. This would be useful with things like the Release Number and Deployable name so that they could be passed to the Jenkins job itself."_ Under advanced settings in the build steps there is an option to tokenise some settings. Is this adequate or would you like something else? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-38633) As a user I want to be able to start a specific stage of a BuildMaster Deployment pipeline.
Title: Message Title Andrew Sumner commented on JENKINS-38633 Re: As a user I want to be able to start a specific stage of a BuildMaster Deployment pipeline. I've released another version which aligns the code with the proget plugin and fixes an issue I found with some requests being cached when running on a slave - probably only affected the proget plugin but I figured it was worth patching this one as well. Also, following up on your comments on the wiki page: "Could you add Token support. This would be useful with things like the Release Number and Deployable name so that they could be passed to the Jenkins job itself." Under advanced settings in the build steps there is an option to tokenise some settings. Is this adequate or would you like something else? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-38633) As a user I want to be able to start a specific stage of a BuildMaster Deployment pipeline.
Title: Message Title Andrew Sumner commented on JENKINS-38633 Re: As a user I want to be able to start a specific stage of a BuildMaster Deployment pipeline. Hi Jon Starbird, I've added another build step called "BuildMaster: Deploy To Stage" in version 1.5. It hasn't had a lot of testing but I wanted to get it out so that you can have a go and give some feedback on it. Let me know what you think. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-38633) As a user I want to be able to start a specific stage of a BuildMaster Deployment pipeline.
Title: Message Title Andrew Sumner commented on JENKINS-38633 Re: As a user I want to be able to start a specific stage of a BuildMaster Deployment pipeline. I've released a new version of the plugin to fix issue JENKINS-37193 whereby the plugin wasn't working at all with version 5 of BuildMaster. Now that is done I can look at this issue - hopefully this won't take long. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-37193) inedo-buildmaster-plugin is Not compatible with BuildMaster 5.x
Title: Message Title Andrew Sumner commented on JENKINS-37193 Re: inedo-buildmaster-plugin is Not compatible with BuildMaster 5.x Version 0.4 of the plugin is now available. It requires a minimum BuildMaster version of 5.5.0. There were a significant amount of changes required to get this working as the BuildMaster API is undergoing a large number of changes at the moment and these haven't fully settled down yet. First, you need to ensure that an api key as been configured in BuildMaster at BuildMaster > Administration > Api Keys & Access Logs. Ensure that the following items are checked: Native API Variables management Release & package deployment I'm currently unable to set the pass a requested BuildNumber to BuildMaster any more - waiting on Inedo for that. I'm unable to get the buildmaster logs - waiting on Inedo to implement a new api endpoint as the old one has been removed. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-37193) inedo-buildmaster-plugin is Not compatible with BuildMaster 5.x
Title: Message Title Andrew Sumner updated an issue Jenkins / JENKINS-37193 inedo-buildmaster-plugin is Not compatible with BuildMaster 5.x Change By: Andrew Sumner Component/s: inedo-buildmaster-plugin Component/s: inedo-proget-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-38633) As a user I want to be able to start a specific stage of a BuildMaster Deployment pipeline.
Title: Message Title Andrew Sumner updated an issue Jenkins / JENKINS-38633 As a user I want to be able to start a specific stage of a BuildMaster Deployment pipeline. Change By: Andrew Sumner Component/s: inedo-buildmaster-plugin Component/s: inedo-proget-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-37193) inedo-buildmaster-plugin is Not compatible with BuildMaster 5.x
Title: Message Title Andrew Sumner commented on JENKINS-37193 Re: inedo-buildmaster-plugin is Not compatible with BuildMaster 5.x Work is underway but hit a snag getting some information I needed using the BuildMaster API, Inedo are working on this and the information will be provided as part of a 5.5 BuildMaster release (I should have access to a beta version in the next day or two). I'll update you when I have more information. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-38633) As a user I want to be able to start a specific stage of a BuildMaster Deployment pipeline.
Title: Message Title Andrew Sumner commented on JENKINS-38633 Re: As a user I want to be able to start a specific stage of a BuildMaster Deployment pipeline. Work is underway but hit a snag getting some information I needed using the BuildMaster API, Inedo are working on this and the information will be provided as part of a 5.5 BuildMaster release (I should have access to a beta version in the next day or two). I'll update you when I have more information. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-37193) inedo-buildmaster-plugin is Not compatible with BuildMaster 5.x
Title: Message Title Andrew Sumner commented on JENKINS-37193 Re: inedo-buildmaster-plugin is Not compatible with BuildMaster 5.x Thanks for the report, I'm looking into this now Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] [gradle-jpi-plugin] (JENKINS-28196) Why is findbugs is listed as a dependancy?
Title: Message Title Andrew Sumner commented on JENKINS-28196 Re: Why is findbugs is listed as a dependancy? When is version 0.11.0 going to be available? Its listed in jCenter but when I attempted to download it, it could not be found. I had a look in https://jcenter.bintray.com/org/jenkins-ci/tools/gradle-jpi-plugin and sure enough its not there. 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] [gradle-jpi-plugin] (JENKINS-28196) Why is findbugs is listed as a dependancy?
Title: Message Title Andrew Sumner created an issue Jenkins / JENKINS-28196 Why is findbugs is listed as a dependancy? Issue Type: Bug Assignee: Daniel Spilker Components: gradle-jpi-plugin Created: 04/May/15 7:11 AM Priority: Minor Reporter: Andrew Sumner Any reason findbugs is listed as a dependancy in the uploaded pom file? Does this mean it's been added to my hpi file? dependency groupIdfindbugs/groupId artifactIdannotations/artifactId version1.0.0/version scoperuntime/scope /dependency http://repo.jenkins-ci.org/releases/com/inedo/buildmaster/inedo-buildmaster/1.1/ (Apologies if I am misusing jira for this question, wasn't sure what was correct forum for this) Add Comment
[JIRA] [gradle-jpi-plugin] (JENKINS-27826) Getting java.lang.NoClassDefFoundError: hudson/matrix/MatrixRun error attempting to run a unit test
Andrew Sumner resolved JENKINS-27826 as Fixed Getting java.lang.NoClassDefFoundError: hudson/matrix/MatrixRun error attempting to run a unit test I'm happy with adding the matrix project dependancy Change By: Andrew Sumner (01/May/15 12:27 AM) Status: Open 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/d/optout.
[JIRA] [gradle-jpi-plugin] (JENKINS-27826) Getting java.lang.NoClassDefFoundError: hudson/matrix/MatrixRun error attempting to run a unit test
Andrew Sumner commented on JENKINS-27826 Getting java.lang.NoClassDefFoundError: hudson/matrix/MatrixRun error attempting to run a unit test That seems to have fixed it, although I ended up adding it as jenkinsTest 'org.jenkins-ci.plugins:matrix-project:1.4@jar'. I'm now getting a huge amount of warnings in in the console output which I can only assume means something isn't quite right (although as this is my first plugin I've got nothing to compare against): WARNING: Failed to load hudson.matrix.MatrixProject java.lang.NoClassDefFoundError: hudson/tasks/test/AggregatedTestResultAction ... WARNING: Failed to scout hudson.matrix.FilterScript$ImpliesWhitelist java.lang.InstantiationException: java.lang.NoClassDefFoundError: org/jenkinsci/plugins/scriptsecurity/sandbox/whitelists/ProxyWhitelist ... My project is https://github.com/andrew-sumner/buildmaster-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] [gradle-jpi-plugin] (JENKINS-27826) Getting java.lang.NoClassDefFoundError: hudson/matrix/MatrixRun error attempting to run a unit test
Andrew Sumner
created JENKINS-27826
Getting java.lang.NoClassDefFoundError: hudson/matrix/MatrixRun error attempting to run a unit test
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
gradle-jpi-plugin
Created:
08/Apr/15 1:41 AM
Description:
I get the following error when trying to run a unit test. Example code is below.
I was able to get past this error by including dependancy testCompile 'org.jvnet.hudson.main:hudson-core:1.159' but that then said other classes where missing. This doesn't see the correct path to go down anyway.
Error
java.lang.NoClassDefFoundError: hudson/matrix/MatrixRun
at com.inedo.TriggerBuildStepTest.init(TriggerBuildStepTest.java:13)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
...
Caused by: java.lang.ClassNotFoundException: hudson.matrix.MatrixRun
at java.net.URLClassLoader$1.run(Unknown Source)
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
... 23 more
Code Example
package test.example;
import static org.junit.Assert.*;
import org.jvnet.hudson.test.JenkinsRule;
import org.apache.commons.io.FileUtils;
import hudson.model.*;
import hudson.tasks.Shell;
import org.junit.Test;
import org.junit.Rule;
public class TriggerBuildStepTest {
@Rule
public JenkinsRule j = new JenkinsRule();
@Test
public void first() throws Exception {
FreeStyleProject project = j.createFreeStyleProject();
project.getBuildersList().add(new Shell("echo hello"));
FreeStyleBuild build = project.scheduleBuild2(0).get();
System.out.println(build.getDisplayName() + " completed");
// TODO: change this to use HtmlUnit
String s = FileUtils.readFileToString(build.getLogFile());
assertTrue(s.contains("+ echo hello"));
}
}
Environment:
dependencies {
classpath org.jenkins-ci.tools:gradle-jpi-plugin:0.10.2
}
Project:
Jenkins
Priority:
Minor
Reporter:
Andrew Sumner
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] [subversion-plugin] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Andrew Sumner edited a comment on JENKINS-18935 Make Subversion plugin support Subversion 1.8 Is there any reason the the update center in Jenkins doesn't find the 2.5 release? It does find 2.4.5 Running latest LTS Jenkins ver. 1.565.3. 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] [subversion-plugin] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Andrew Sumner commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 Is there any reason the the update center in Jenkins doesn't find the 2.5 release? It does find 2.5.4. Running latest LTS Jenkins ver. 1.565.3. 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.
