Re: How to release plugin when using git 1.8.5.2
Thanks for sharing! Can you please paste this recipe into the wiki dev page? Am 16.06.2014 um 22:32 schrieb Marco Miller miller.ma...@me.com: Just thought I could share this not-so-new info, in case anybody struggles with this like I just did..: assuming you're using a version of git around 1.8.5.2 (the one I use) I use maven 3.1.1, but that is just FYI you'll need to force maven-release-plugin 2.5, as per later below (otherwise your release will fail committing the non-SNAPSHOT) make sure your git origin is your actual plugin repo to release (jenkinsci/pluginToRelease) if your jenkins-ci and github accounts' credentials differ, have this in your maven settings.xml: servers server idmaven.jenkins-ci.org/id usernameyourJenkinsCIuser/username passwordyourJenkinsCIpwd/password /server /servers cd to your plugin git repo to release mvn org.apache.maven.plugins:maven-release-plugin:2.5:prepare then, if all looks fairly ok, mvn org.apache.maven.plugins:maven-release-plugin:2.5:perform (you can combine the above commands into one, say, next time you release..) I had to also do a git push, even though that looked more like a no-op (but then git status disagreed) so, the above allowed me to make release 1.9 of github.com/jenkinsci/description-setter-plugin (e.g.) references I used to come up with the above: groups.google.com/forum/#!topic/jenkinsci-dev/qkmbl3HrYgk jenkins-ci.361315.n4.nabble.com/Unable-to-deploy-plugin-to-repo-tc3093159.html#a3093270 wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-PreparePOMforrelease -The last ref above (3.) is of particular importance; you need to follow it.. /Marco -- 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. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Message signed with OpenPGP using GPGMail
Is there anything suggestion to build with codes which are not submitted?
We have a test framework to work with codes which are not submitted. If Jenkins can support this feature, we will try to integrate it to our framework. -- 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. For more options, visit https://groups.google.com/d/optout.
*.jenkins-ci.org server stability?
Not sure if this is normally the place to mention stuff like this, but *.jenkins-ci.org seem to be unstable for the last day (updates.jenkins-ci.org etc). What normally happens to investigate + rectify this? Regards, T. -- 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. For more options, visit https://groups.google.com/d/optout.
Re: *.jenkins-ci.org server stability?
On Tue, Jun 17, 2014 at 10:00 AM, Tom Fennelly tom.fenne...@gmail.com wrote: Not sure if this is normally the place to mention stuff like this Here or in the #jenkins-infra chat room. Yes the site has been having a lot of problems. AFAIK there is no single person charged with investigating and addressing all such issues. -- 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. For more options, visit https://groups.google.com/d/optout.
Re: *.jenkins-ci.org server stability?
It's a PITA :) On 17/06/2014 15:07, Jesse Glick wrote: On Tue, Jun 17, 2014 at 10:00 AM, Tom Fennelly tom.fenne...@gmail.com wrote: Not sure if this is normally the place to mention stuff like this Here or in the #jenkins-infra chat room. Yes the site has been having a lot of problems. AFAIK there is no single person charged with investigating and addressing all such issues. -- 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. For more options, visit https://groups.google.com/d/optout.
Re: How to release plugin when using git 1.8.5.2
Good idea Ulli! = done; here is the change, fyi: https://wiki.jenkins-ci.org/pages/diffpages.action?pageId=18612226originalId=72778548 2014-06-17 3:16 GMT-04:00 Ulli Hafner ullrich.haf...@gmail.com: Thanks for sharing! Can you please paste this recipe into the wiki dev page? Am 16.06.2014 um 22:32 schrieb Marco Miller miller.ma...@me.com: Just thought I could share this not-so-new info, in case anybody struggles with this like I just did..: 1. assuming you're using a version of git around 1.8.5.2 (the one I use) 2. I use maven 3.1.1, but that is just FYI 3. you'll need to force maven-release-plugin 2.5, as per later below 4. (otherwise your release will fail committing the non-SNAPSHOT) 5. make sure your git origin is your actual plugin repo to release ( jenkinsci/pluginToRelease) 6. if your jenkins-ci and github accounts' credentials differ, have this in your maven settings.xml: servers server idmaven.jenkins-ci.org/id usernameyourJenkinsCIuser/username passwordyourJenkinsCIpwd/password /server /servers 7. cd to your plugin git repo to release 8. mvn org.apache.maven.plugins:maven-release-plugin:2.5:prepare 9. then, if all looks fairly ok, 10. mvn org.apache.maven.plugins:maven-release-plugin:2.5:perform 11. (you can combine the above commands into one, say, next time you release..) 12. I had to also do a git push, even though that looked more like a no-op (but then git status disagreed) 13. so, the above allowed me to make release 1.9 of github.com/jenkinsci/description-setter-plugin (e.g.) 14. references I used to come up with the above: 1. groups.google.com/forum/#!topic/jenkinsci-dev/qkmbl3HrYgk 2. jenkins-ci. 361315.n4.nabble.com/Unable-to-deploy-plugin-to-repo-tc3093159.html#a3093270 3. wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-PreparePOMforrelease -The last ref above (3.) is of particular importance; you need to follow it.. /Marco -- 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. 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. For more options, visit https://groups.google.com/d/optout.
Aw: Re: How to release plugin when using git 1.8.5.2
I have those problems too and spend hours of work: - http://stackoverflow.com/questions/24198976 - http://stackoverflow.com/questions/24062982 I will folow your suggestions and finally release my plugin. Thanks for sharing! Can you please paste this recipe into the wiki dev page? Am 16.06.2014 um 22:32 schrieb Marco Miller miller.ma...@me.com: Just thought I could share this not-so-new info, in case anybody struggles with this like I just did..: assuming youre using a version of git around 1.8.5.2 (the one I use) I use maven 3.1.1, but that is just FYI youll need to force maven-release-plugin 2.5, as per later below (otherwise your release will fail committing the non-SNAPSHOT) make sure your git origin is your actual plugin repo to release (jenkinsci/pluginToRelease) if your jenkins-ci and github accounts credentials differ, have this in your maven settings.xml: servers server idmaven.jenkins-ci.org/id usernameyourJenkinsCIuser/username passwordyourJenkinsCIpwd/password /server /servers cd to your plugin git repo to release mvn org.apache.maven.plugins:maven-release-plugin:2.5:prepare then, if all looks fairly ok, mvn org.apache.maven.plugins:maven-release-plugin:2.5:perform (you can combine the above commands into one, say, next time you release..) I had to also do a git push, even though that looked more like a no-op (but then git status disagreed) so, the above allowed me to make release 1.9 ofgithub.com/jenkinsci/description-setter-plugin (e.g.) references I used to come up with the above: groups.google.com/forum/#!topic/jenkinsci-dev/qkmbl3HrYgk jenkins-ci.361315.n4.nabble.com/Unable-to-deploy-plugin-to-repo-tc3093159.html#a3093270 wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-PreparePOMforrelease -The last ref above (3.) is of particular importance; you need to follow it.. /Marco -- 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. 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. For more options, visit https://groups.google.com/d/optout.
Re: New naming: Item vs. Job
I created a new branch with my suggested changes: https://github.com/jenkinsci/jenkins/compare/master...new-rename This short form will also have the benefit that it automatically produces grammatically correct labels for non-english languages (e.g., in German). I think it is always a bad idea to concatenate two localized texts, this might work in English but not in German. I haven’t yet changed the descriptor labels yet. Am 18.03.2014 um 18:17 schrieb Jesse Glick jgl...@cloudbees.com: On Tue, Mar 18, 2014 at 1:09 PM, Ulli Hafner ullrich.haf...@gmail.com wrote: New … Good idea, this would work. I would also propose renaming descriptors like ‘Build a free-style software project’ to use noun phrases, not verb phrases. The newJobDetail.jelly blurb beneath would not necessarily need to change. -- 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. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Message signed with OpenPGP using GPGMail
Re: Dynamic Provisioning of windows slaves using ssh
Hi there!
I belive you are not alone in the struggle of using SSH to windows slaves.
However, we do use vanilla SSHSlaves plugin for that and it works perfectly
-- with regard to the paths part.
On Tuesday, June 17, 2014 3:44:08 AM UTC+4, Suresh Nallamilli wrote:
Hi All,
I am working on a sample plugin to dynamically provision windows slaves.
Windows slave images are preconfigred with SSH server(cygwin openssh
server),
so after provionsing - machine comes up with ssh server installed.
Once the slave is up , I am able to copy slave.jar and also able to
execute commands using ssh.
However when I try to set the channel using below code – getting error
(see below stack trace)
computer.setChannel(sess.getStdout(),sess.getStdin(),logger,new Listener()
{
public void onClosed(Channel channel, IOException cause) {
sess.close();
conn.close();
}
});
*Question:*
1) Is windows slaves launch supported via ssh?
What steps I need to take care to add ssh launch method support for
windows slaves?
I am not seeing ssh support for windows slaves when adding node
manually , so wondering if this is supported or not?
Stack Trace:
java.io.EOFException: unexpected stream termination
at
hudson.remoting.ClassicCommandTransport.create(ClassicCommandTransport.java:100)
at hudson.remoting.Channel.init(Channel.java:392)
at hudson.remoting.Channel.init(Channel.java:388)
at hudson.remoting.Channel.init(Channel.java:349)
at hudson.remoting.Channel.init(Channel.java:345)
Thanks,
Suresh Nallamilli.
--
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.
For more options, visit https://groups.google.com/d/optout.
Re: New naming: Item vs. Job
On Tue, Jun 17, 2014 at 4:04 PM, Ulli Hafner ullrich.haf...@gmail.com wrote:
I think it is always a bad idea to concatenate two localized texts, this
might work in English but not in German.
Right, it is an I18N violation to concatenate localized strings. This
will happen to work in English and some other languages (Khmer maybe),
but will tend to break when there is an inflected case system, or
grammatical genders, or various other conditions. Localized values
should be treated as opaque sentences or smaller syntactic phrases.
BTW when changing the number of format arguments to a key (such as
changing the English value from ‘New {0}’ to ‘New’), you should pick a
new key name. Otherwise there can be a compatibility issue in
MessageFormat.
--
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.
For more options, visit https://groups.google.com/d/optout.
Re: New naming: Item vs. Job
On 17.06.2014, at 22:04, Ulli Hafner ullrich.haf...@gmail.com wrote: suggested changes An ellipsis at the end of an action label usually indicates that further input is required rather than that an action is taken immediately. While it could mean that in this case, this would be the only link in Jenkins that I know of that uses an the ellipsis as part of the label. Users aware of this very common convention would just be confused by this inconsistency. https://developer.apple.com/library/mac/documentation/UserExperience/Conceptual/AppleHIGuidelines/TextStyle/TextStyle.html#//apple_ref/doc/uid/TP3365-TPXREF126 When it appears in the name of a button or a menu item, an ellipsis character (...) indicates to the user that additional information is required before the associated operation can be performed. Specifically, it prepares the user to expect the appearance of a window or dialog in which to make selections or enter information before the command executes. http://msdn.microsoft.com/en-us/library/dn742392.aspx#usingellipses While menu commands are used for immediate actions, more information might be needed to perform the action. Indicate a command that needs additional information (including a confirmation) by adding an ellipsis at the end of the label. https://en.wikipedia.org/wiki/Common_User_Architecture#Description Menu commands that require parameters to proceed are suffixed with an ellipsis (...); -- 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. For more options, visit https://groups.google.com/d/optout.
Re: New naming: Item vs. Job
I don’t understand: this is actually the case for ’New…’. After pressing the link a new dialog with name and radio button opens. Unless you save the following dialog no new element is created. Am 17.06.2014 um 23:22 schrieb Daniel Beck m...@beckweb.net: On 17.06.2014, at 22:04, Ulli Hafner ullrich.haf...@gmail.com wrote: suggested changes An ellipsis at the end of an action label usually indicates that further input is required rather than that an action is taken immediately. While it could mean that in this case, this would be the only link in Jenkins that I know of that uses an the ellipsis as part of the label. Users aware of this very common convention would just be confused by this inconsistency. https://developer.apple.com/library/mac/documentation/UserExperience/Conceptual/AppleHIGuidelines/TextStyle/TextStyle.html#//apple_ref/doc/uid/TP3365-TPXREF126 When it appears in the name of a button or a menu item, an ellipsis character (...) indicates to the user that additional information is required before the associated operation can be performed. Specifically, it prepares the user to expect the appearance of a window or dialog in which to make selections or enter information before the command executes. http://msdn.microsoft.com/en-us/library/dn742392.aspx#usingellipses While menu commands are used for immediate actions, more information might be needed to perform the action. Indicate a command that needs additional information (including a confirmation) by adding an ellipsis at the end of the label. https://en.wikipedia.org/wiki/Common_User_Architecture#Description Menu commands that require parameters to proceed are suffixed with an ellipsis (...); -- 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. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Message signed with OpenPGP using GPGMail
Re: New naming: Item vs. Job
On 17.06.2014, at 23:46, Ulli Hafner ullrich.haf...@gmail.com wrote: I don't understand: this is actually the case for 'New...'. Yes, and that gives the impression that Jenkins actually follows this convention (this is the first sidepanel item anyone sees after all), which it doesn't. -- 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. For more options, visit https://groups.google.com/d/optout.
Re: New naming: Item vs. Job
Any better ideas then? Am 17.06.2014 um 23:54 schrieb Daniel Beck m...@beckweb.net: On 17.06.2014, at 23:46, Ulli Hafner ullrich.haf...@gmail.com wrote: I don't understand: this is actually the case for 'New...'. Yes, and that gives the impression that Jenkins actually follows this convention (this is the first sidepanel item anyone sees after all), which it doesn't. -- 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. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Message signed with OpenPGP using GPGMail
Re: What parts of the source code would affect iframe embedding in the job description?
iframes are rejected for security reasons. If you do not care about security, install the Anything Goes Formatter. -- 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. For more options, visit https://groups.google.com/d/optout.
Re: New naming: Item vs. Job
On Tue, Jun 17, 2014 at 5:54 PM, Daniel Beck m...@beckweb.net wrote: that gives the impression that Jenkins actually follows this convention Well, it sets a good precedent then. -- 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. For more options, visit https://groups.google.com/d/optout.
Re: What parts of the source code would affect iframe embedding in the job description?
On 17.06.2014, at 23:58, Chris Tutty christu...@gmail.com wrote: Raw HTML Could someone please do a release of that plugin? This has come up way too often... https://github.com/jenkinsci/antisamy-markup-formatter-plugin/pull/1 -- 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. For more options, visit https://groups.google.com/d/optout.
Re: Problems building maven-plugin in Eclipse
Hi, I am getting the same error. Can anyone provide the solution for this? I am using Eclipse Kepler. On Friday, 15 November 2013 10:29:28 UTC-8, kutzi wrote: Hi, I had several problems with building Jenkins/maven-plugin in the past, but the errors I'm getting now are especial nasty: Eclipse e.g. complains that it cannot find hudson.model.Queue.Item (in MavenModuleSet) and several other compile errors. I checked the the Jenkins core jar is intact (building with mvn works) and no amount of refreshing in Eclipse and the usual other tricks to get it working again got me anywhere. Did anyone have similar problems and maybe a solution? Eclipse Kepler 4.3.1, M2e 1.4.0 - Kutzi -- 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. For more options, visit https://groups.google.com/d/optout.
Re: What parts of the source code would affect iframe embedding in the job description?
On Tue, Jun 17, 2014 at 7:58 PM, Daniel Beck m...@beckweb.net wrote: Could someone please do a release of that plugin? Done. -- 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. For more options, visit https://groups.google.com/d/optout.
Re: Query about jenkins source code
In the future, please direct questions like this to the jenkinsci-dev list. As to your question, see https://wiki.jenkins-ci.org/display/JENKINS/Action+and+its+family+of+subtypes and hopefully this gets you to the right place. 2014-06-17 16:13 GMT-07:00 Shantaraman, Karthik kshantara...@ebay.com: Hi Kohsuke, I am looking to extend the Jenkins Source code and adding an extra link to the side nav that contains the following set of links http://localhost:8080/ Back to Dashboard http://localhost:8080/ http://localhost:8080/job/pluginTest/ *Status* http://localhost:8080/job/pluginTest/ http://localhost:8080/job/pluginTest/changes Changes http://localhost:8080/job/pluginTest/changes http://localhost:8080/job/pluginTest/ws/ Workspace http://localhost:8080/job/pluginTest/ws/ http://localhost:8080/job/pluginTest/build?delay=0sec Build Now http://localhost:8080/job/pluginTest/build?delay=0sec http://localhost:8080/job/pluginTest/# Delete Maven project http://localhost:8080/job/pluginTest/# http://localhost:8080/job/pluginTest/configure Configure http://localhost:8080/job/pluginTest/configure http://localhost:8080/job/pluginTest/modules Modules http://localhost:8080/job/pluginTest/modules Since the source code is very vast, I am unsure of where to look in the source code to find the existing code for these links. Is it possible for you to help me with it and provide a guidance on how to proceed? Thanks, Karthik -- 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. For more options, visit https://groups.google.com/d/optout.
My notes on getting started with Workflow plugin
I was playing with workflow plugin, thought will share my notes. My test script is based on cd.groovy https://github.com/jenkinsci/workflow-plugin/blob/master/aggregator/cd.groovy script from workflow-plugin repo. My notes at: *https://gist.github.com/vivek/8f3ba9e4cfce8ba5e3f6 https://gist.github.com/vivek/8f3ba9e4cfce8ba5e3f6* Instead of building the workflow-plugin from source you can also download it's experimental beta version that Jesse released this afternoon.. Testing with master and slave running on the same host was almost straight forward, *almost* incase you are new to docker. Although I ended up spending some time trying to get port forwarding to work between host and guest vm with Docker 1.0 on Mac. I gave up after realizing it's busted, see https://github.com/boot2docker/boot2docker/issues/395. So I ended up running Jetty on the docker VM on my ubuntu box which was pretty easy. In another setup I ran Jenkins slave on a remote host on a docker a VM. Had to have my Dockerfile based off evarga/jenkins-slave, primarily to install curl package and generate ssh keys. SSH keys are important for the portion of your job running on this remote slave to deploy the war to staging and production endpoint on the Jetty - that is running on another VM. If you are planning to experiment on running remote slave, use this workflow script: https://gist.github.com/vivek/c3767376f714e794455d. Pretty cool stuff! vivek. -- 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. For more options, visit https://groups.google.com/d/optout.
