Re: Jenkins doesn't launch when debugging with hpi:run
Hi, I followed the plugin tutorial yesterday with least load plugin. I couldn't open http://localhost:8080/jenkins after mvn hpi:run Instead, I found out Jenkins is running at http://localhost:8080 I am not sure it is the same problem you are facing, but I hope it helps. //Jifeng On Tuesday, August 5, 2014 9:36:03 PM UTC+2, Michael Alexander wrote: I'm trying to debug my plugin as described in the Jenkins plugin tutorial. I follow all the instructions for creating the default plugin. Everything works fine until I try debugging using mvn hpi:run. The jetty server starts and allows me to reload it, but Jenkins never launches. I've tried debugging other plugins that I've taken from github, and they usually debug fine (Jenkins launches). I looked at my pom.xml and compared it to working plugins, but couldn't seem to get it to work. Any recommendations? I'm using Maven 3.2.1. -- View this message in context: http://jenkins-ci.361315.n4.nabble.com/Jenkins-doesn-t-launch-when-debugging-with-hpi-run-tp4713146.html Sent from the Jenkins dev mailing list archive at Nabble.com. -- 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 programmatically access the POM version number
please fill an issue or even better: send a PR with a fix Domi On 04.08.2014, at 16:18, pallen pal...@perforce.com wrote: Found a BUG in the digit(index) method in hudson.util.VersionNumber. The item value never gets updated, so you only get the first entry back regardless of the index. On Monday, August 4, 2014 2:30:29 PM UTC+1, pallen wrote: Jenkins.getInstance().getUpdateCenter().getPlugin(p4).getInstalled().getPlugin().getWrapper().getVersion(); gives: 1.0.10-SNAPSHOT (private-08/04/2014 14:27-pallen) Seems convoluted, but does the job. Thanks for the hint. Paul On Monday, August 4, 2014 2:21:49 PM UTC+1, pallen wrote: I can get this far... Jenkins.getInstance().getUpdateCenter().getPlugin(p4) but can't find a getWrapper() On Monday, August 4, 2014 1:57:08 PM UTC+1, Dominik Bartholdi wrote: As this should always match the plugin version, you can do something like this: Jenkins.getUpdateCenter().getPlugin(p4).getWrapper().getVersion() ...just out of my head - please check concrete method names... Domi On 04.08.2014, at 14:52, pallen pal...@perforce.com wrote: In my POM I specify the plugin's version, e.g. artifactIdp4/artifactId version1.0.9/version packaginghpi/packaging I would like to access the String 1.0.9 in my code; something like this: this.getClass().getPackage().getImplementationVersion(); I have tried adding the maven-jar-plugin as per http://stackoverflow.com/questions/3697449/retrieve-version-from-maven-pom-xml-in-code, but no luck. Is this a result of the HPI packaging? Kind regards, Paul -- 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-de...@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. -- 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.
Agenda is up for Jenkins CI User Event, CPH
Hi all, Hope everyone has enjoyed the summer! We're happy to announce that the agenda for The Jenkins CI User Event in Copenhagen http://www.jcicph.dk is now up! Once again the line-up looks pretty great - check it out! And while you're at it, check out the Jenkins CI Code Camp Aug. 21st, the day prior to the User Event. - Jenkins CI User Event, CPH - Aug 22nd http://www.jcicph.dk/agenda - Jenkins CI Code Camp, CPH - Aug 21st http://www.jcicph.dk/codecamp/ Please help us drive sign-ups by promoting the agenda in your network and tweet about it with @jcicph http://www.twitter.com/jcicph #jcicph http://www.twitter.com/jcicph We appreciate any help spreading the word and look forward to some great days in Copenhagen! Best Regards, The Praqma Team [image: ] http://www.google.com/url?q=http%3A%2F%2Fwww.praqma.com%2Fsa=Dsntz=1usg=AFrqEzfM8UoW1eZZd9XBldWhYgoA5DqfVw *Adam Henriques* Sales Marketing a...@praqma.net +45 28129094 *Praqma A/S* www.praqma.net http://www.google.com/url?q=http%3A%2F%2Fwww.praqma.netsa=Dsntz=1usg=AFrqEzeVZLYSjJ0m5TWnjOGLvDADa9_tYg Allerød Stationsvej 4 DK-3450 Allerød +45 36 77 27 62 [image: www.jcicph.dk] http://www.jcicph.dk -- 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 doesn't launch when debugging with hpi:run
Thanks for the suggestion, but unfortunately this isn't my issue. Jenkins isn't launching at all, just the Jetty server. -- View this message in context: http://jenkins-ci.361315.n4.nabble.com/Jenkins-doesn-t-launch-when-debugging-with-hpi-run-tp4713146p4713739.html Sent from the Jenkins dev mailing list archive at Nabble.com. -- 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.getAuthentication()
Hi dev list,
I'm implementing an action in which I want to get the logged in user.
The following code:
public void computeLoggedInUserName() {
final Object principal = Jenkins.getAuthentication().getPrincipal();
if (principal instanceof Details) {
loggedInUserName = ((Details)principal).getUsername();
return;
}
if (principal instanceof LdapUserDetails) {
loggedInUserName = ((LdapUserDetails)principal).getUsername();
return;
}
loggedInUserName = anonymous;
}
was doing the job.
Since I migrated to 1.554.X LTS version (same for latest LTS: 1.565.1),
this method always return anonymous even
if Jenkins.getAuthentication().isAuthenticated() return true.
Is it a regression or am I doing it the wrong way?
Thanks for your help.
--
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: Discussion: Refactoring of JENKINS project in JIRA
Update on Action #1.b: - The Wiki page seems to be finalized (in the scope of component changes) - All actions seem to be categorized - There were many contributions from other people - No unhandled comments from the mailing list/IRC - No new comments over 1 month - I've started the update of Jenkins IRC Bot in order to simplify the modification process: - Issue on Jenkins JIRA: https://issues.jenkins-ci.org/browse/INFRA-100 - https://github.com/jenkins-infra/ircbot/pull/11 - https://github.com/jenkinsci/lib-jira-scraper/pull/1 - Unfortunately, there's no responses. I have no JIRA installations to test new jira-scraper routines - Workflow changes: Untriaged and Waiting on requester states - The description has not been finalized yet - BTW, both states have been discussed in IRC/mailing list. There should not be any blockers Best regards, Oleg Nenashev 2014-08-06 9:32 GMT+04:00 Oleg Nenashev o.v.nenas...@gmail.com: Summary from the previous Project meeting (thanks to Daniel Beck for the notification). 1. *JIRA components* (jglick http://meetings.jenkins-ci.org/jenkins/2014/jenkins.2014-07-23-18.02.log.html#l-59, 18:18:39) 1. https://wiki.jenkins-ci.org/display/JENKINS/2014+JIRA+Components+Refactoring (danielbeck http://meetings.jenkins-ci.org/jenkins/2014/jenkins.2014-07-23-18.02.log.html#l-62, 18:19:33) 2. *ACTION*: oleg-nenashev to report on status of JIRA component change (jglick http://meetings.jenkins-ci.org/jenkins/2014/jenkins.2014-07-23-18.02.log.html#l-72, 18:22:31) 3. *ACTION*: kohsuke to implement JIRA component change (jglick http://meetings.jenkins-ci.org/jenkins/2014/jenkins.2014-07-23-18.02.log.html#l-73, 18:22:39) 4. *AGREED*: want unsorted component empty, but maybe need a more descriptive name (jglick http://meetings.jenkins-ci.org/jenkins/2014/jenkins.2014-07-23-18.02.log.html#l-99, 18:27:51) 2. *JIRA components* (jglick http://meetings.jenkins-ci.org/jenkins/2014/jenkins.2014-07-23-18.02.log.html#l-106, 18:29:07) 1. *ACTION*: oleg-nenashev to document intended usage of unsorted ( jglick http://meetings.jenkins-ci.org/jenkins/2014/jenkins.2014-07-23-18.02.log.html#l-113, 18:31:13) I'll try to send a summary on my actions in advance. BR, Oleg Nenashev вторник, 24 июня 2014 г., 21:37:43 UTC+4 пользователь Oleg Nenashev написал: Since there's no additional input on the components modification, I propose to apply changes on JIRA. Thanks to R. Tyler and OSUOSL, Jenkins JIRA is stable enough for such changes now. If everyone agrees, it would be great if somebody with JIRA administration rights takes the action point. Actions backlog: - Describe the workflow modification for JIRA project - Untriaged state for new issues (see Kohsuke's clarification above) - [New] - Waiting on user state - for incomplete issues Best regards, Oleg Nenashev 2014-06-10 18:41 GMT+04:00 Jesse Glick jgl...@cloudbees.com: On Tue, Jun 10, 2014 at 3:34 AM, Daniel Beck m...@beckweb.net wrote: Confused it with the Maven build step that's part of core. (but which ought to be a plugin too) -- You received this message because you are subscribed to a topic in the Google Groups Jenkins Developers group. To unsubscribe from this topic, visit https://groups.google.com/d/ topic/jenkinsci-dev/luOqm4Qj4sc/unsubscribe. To unsubscribe from this group and all its topics, 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 a topic in the Google Groups Jenkins Developers group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/luOqm4Qj4sc/unsubscribe. To unsubscribe from this group and all its topics, 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.
Backporting for 1.565.2 is finished
Hi, Backporting changes for 1.565.2 is completed. Fixed issues: https://issues.jenkins-ci.org/secure/IssueNavigator.jspa?reset=truejqlQuery=labels+%3D+%221.565.2-fixed%22 Somehow I forgot to announce that backporting started. Sorry about that. -- oliver -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Backporting for 1.565.2 is finished
On Wed, Aug 6, 2014 at 10:03 AM, oliver gondža ogon...@gmail.com wrote: Backporting changes for 1.565.2 is completed. I would suggest including https://issues.jenkins-ci.org/browse/JENKINS-22641 despite its recent fix, given the severity of the bug, the fact that it was a regression, and the simplicity of the patch. -- 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 doesn't launch when debugging with hpi:run
On Wed, Aug 6, 2014 at 12:06 AM, Jifeng Zhang zjfr...@gmail.com wrote: I followed the plugin tutorial yesterday with least load plugin. I couldn't open http://localhost:8080/jenkins after mvn hpi:run Instead, I found out Jenkins is running at http://localhost:8080 Then either you are using a rather old version of maven-hpi-plugin, or your plugin has explicitly overridden the test context path. -- 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.getAuthentication()
On Wed, Aug 6, 2014 at 6:39 AM, David Rautureau drautur...@gmail.com wrote: Is it a regression or am I doing it the wrong way? Not sure if there is a regression in intended/documented functionality, but anyway all you need to do is: return Jenkins.getAuthentication().getName(); -- 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.
New Plugin: SAML Plugin
Hi, I created a SAML 2.0 Authentication plugin: https://github.com/connectifier/jenkins-saml-plugin My GitHub ID is benmccann Thanks, Ben -- 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.
