date:20130303

buildhive

2013-03-03 Thread nicolas de loof

I've disabled buildhive CI for jenkins-core (
https://buildhive.cloudbees.com/job/jenkinsci/job/jenkins/) as builds all
fail with timeout
and configured https://jenkins.ci.cloudbees.com/job/core to monitor
pull-requests. I have more control on this one to tweak the build.

-- 
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/groups/opt_out.

jenkins with vss

2013-03-03 Thread miscuse0

I am getting the following error while i try to use continuous integration 
-- jenkins with vss plugin.. please pour in ur thoughts
 
Error:
 
 
Unable to open database \\serverpath\srcsafe.ini hudson.util.IOException2: 
com4j.ComException: 8004d845 (Unknown error) : Invalid DOS path: 
j:\xxx\xxx\data\um.dat : .\invoke.cpp

 

appreciate any 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/groups/opt_out.

How to determine which revision was built with a build?

2013-03-03 Thread Georg Gruetter

Hi everyone,

I'm writing a build notifier for Stash 
(stashNotifier) 
and I need to determine which revision was built in order to correctly 
notify Stash. In the case of Git, I need to know the commit id. The commit 
Id shows up properly in the Jenkins build job log, e. g. 

Last Built Revision: Revision 90b8fd0f8f6d3bfbf3c1438d82a1a9ce9be8fb4c 
(origin/HEAD, origin/develop)
Fetching changes from 1 remote Git repository
Fetching upstream changes from origin
Seen branch in repository origin/HEAD
Seen branch in repository origin/develop
Seen branch in repository origin/feature-1
Commencing build of Revision 6a111c77b967a33a1aaea5d4330ce1cc7ccc991b 
(origin/feature-1)


But how can I access this information? I'm currently using 
AbstractBuild.getChangeSet(), but that doesn't work for me, as the following 
scenario shows:


   1. I make a commit on branch develop
   2. I make another commit on branch feature/1
   3. I push both branches
   4. Jenkins picks up the changes on both branches and starts a dedicated 
   builds for each of them
   5. The first build picks up the changes on the develop branch (with 
   AbstractBuild.getChangeSet())
   6. The second build does not pick up any changes at all.

I couldn't find anything in the JavaDoc for AbstractBuild, Run and 
Actionable. I'd appreciate it if anyone could point me in the right 
direction.

Thanks in advance and cheers,

Georg

-- 
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/groups/opt_out.

RE: Jenkins and MKS inegration

2013-03-03 Thread Cletus D'Souza


Hi, Take a look at the command being executed: si projectinfo --user=jasam 
--port=7001 --hostname=sal-vs-mks01.corp.svbank.com 
--project=#/projects/ClientOnBoarding/SVBClientOnBoardingHTML/project.pj#b=1.1 
Try to reproduce this error using the Integrity CLI.  If you have reproduced 
this error, then contact PTC Customer Support as this is a problem with 
Integrity in your environment and not the plugin. Thanks!Cletus
 Date: Wed, 27 Feb 2013 10:23:21 -0800
From: jaggi@gmail.com
To: jenkinsci-dev@googlegroups.com
Subject: Jenkins and MKS inegration

Getting below issue after installing Integrity plug in and initiating build.
 
Started by user anonymousBuilding in workspace C:\Program 
Files\Jenkins\jobs\test\workspaceChange Log: 
http://localhost:8080/job/test/15/changesBuild Log: 
http://localhost:8080/job/test/15/consolePreparing to execute si projectinfo 
for #/projects/ClientOnBoarding/SVBClientOnBoardingHTML/project.pj#b=1.1An API 
Exception was caught!The project 
#/projects/ClientOnBoarding/SVBClientOnBoardingHTML/project.pj#b=1.1 could not 
be located on the server sal-vs-mks01.corp.svbank.com:7001: MKS125343: The 
project /projects/ClientOnBoarding/SVBClientOnBoardingHTML/project.pj does not 
exist.si projectinfo --user=jasam --port=7001 
--hostname=sal-vs-mks01.corp.svbank.com 
--project=#/projects/ClientOnBoarding/SVBClientOnBoardingHTML/project.pj#b=1.1 
-- returned exit code 128
Finished: FAILURE
 
Please help me



-- 

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/groups/opt_out.

 

 
  

-- 
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/groups/opt_out.

Wiki page not updating after edit

2013-03-03 Thread Bap

I am unable to update the wiki page at  
https://wiki.jenkins-ci.org/display/JENKINS/Publish+Over+...

I have created 2 new versions (v.29 on 22/10/2010 and v.30 today)

Just below the page heading it states that the page was last updated  
on 10/09/2012 (v. 28)


When I edit the page, the source is correct, but when viewing, the  
page is 5 months old!


Is something failing to generate a new "static" version of the page  
after a save or is there some other cache invalidation that is not  
happening?



--
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/groups/opt_out.

Re: mvn release does not work, only publishes SNAPSHOT releases

2013-03-03 Thread Georg Gruetter

Hi Baptiste,

* upgrade to mvn 3.0.4 or 3.0.5, 3.0.3 have had some issues that even led 
jenkins core to forbid building with it
I already upgraded to 3.0.5 but the problem persists.

* which mvn-release-p version are you using? 2.4 has some issues with git. 
> Prefer sticking to 2.3.2 before it's fixed.
>
I'm using  2.2.2 as prescribed by the jenkins parent pom version 1.498. 
I'll try manually setting 2.3.2 when I do the next release. Thanks for the 
tip.

Cheers,
Georg

Le 1 mars 2013 01:36, "Georg Gruetter" > a 
écrit :

> Hi all,
>
> this is a followup of a thread I started 
> earlier.
>  
> I'm trying to publish my first release of the stashnotifier 
> pluginbut continue to 
> fail. Here's what happens
>
>1. I am ready to perform a maven release (SNAPSHOT version, all 
>changes committed and pushed to GitHub). I'm on the develop branch (I 
>usually use the git-flow branching model and tried the same on a release 
>branch - same problem. I haven't tried this on the master branch though).
>2. I perform mvn release:prepare release:perform
>3. When prompted for the release version, I enter 1.0.2 (current + 
>next SNAPSHOT version is 1.1-SNAPSHOT)
>4. the release runs through successfully without any error but only 
>publishes the SNAPSHOT version 
>
> I think the problem occurs in the release:prepare. After release:prepare, 
> I'd expect so see a commit in my local repository where the artifact 
> version in my pom.xml is set to the release version (1.0.2). However - no 
> commit. As a result, the artifact version is still 1.1-SNAPSHOT and I guess 
> that's why maven decides to deploy it to the SNAPSHOTS repository. Tagging 
> works and the tag is also pushed to the remote.
>
> From what I can tell, maven sort of omits the commit command and no 
> changes are pushed as a result:
>
>> [INFO] Checking in modified POMs...
>> [INFO] Executing: /bin/sh -c cd /Users/gruetter/Dropbox/stashNotifier && 
>> git add -- pom.xml
>> [INFO] Working directory: /Users/gruetter/Dropbox/stashNotifier
>> [INFO] Executing: /bin/sh -c cd /Users/gruetter/Dropbox/stashNotifier && 
>> git status
>> [INFO] Working directory: /Users/gruetter/Dropbox/stashNotifier
>> [INFO] Tagging release with the label stashNotifier-1.0.2...
>> [INFO] Executing: /bin/sh -c cd /Users/gruetter/Dropbox/stashNotifier && 
>> git tag -F 
>> /var/folders/dr/xxbtyycs1z9dl2_snlj87zrhgn/T/maven-scm-678409272.commit 
>> stashNotifier-1.0.2
>> [INFO] Working directory: /Users/gruetter/Dropbox/stashNotifier
>> [INFO] Executing: /bin/sh -c cd /Users/gruetter/Dropbox/stashNotifier && 
>> git push g...@github.com:jenkinsci/stashnotifier-plugin.git 
>> stashNotifier-1.0.2
>> [INFO] Working directory: /Users/gruetter/Dropbox/stashNotifier
>> [INFO] Executing: /bin/sh -c cd /Users/gruetter/Dropbox/stashNotifier && 
>> git ls-files
>> [INFO] Working directory: /Users/gruetter/Dropbox/stashNotifier
>> [INFO] Transforming 'Stash Notifier'...
>> [INFO] Not removing release POMs
>> [INFO] Checking in modified POMs...
>> [INFO] Executing: /bin/sh -c cd /Users/gruetter/Dropbox/stashNotifier && 
>> git add -- pom.xml
>> [INFO] Working directory: /Users/gruetter/Dropbox/stashNotifier
>> [INFO] Executing: /bin/sh -c cd /Users/gruetter/Dropbox/stashNotifier && 
>> git status
>> [INFO] Working directory: /Users/gruetter/Dropbox/stashNotifier
>> [INFO] Release preparation complete.
>>
>
> I have appended the complete mvn output of the release run for your 
> reference. I'm running Maven 3.0.3, by the way. Can anyone please tell me 
> what I'm doing wrong? I'm banging my head against the wall on this for a 
> couple of days now.
>
> Thanks for your help and cheers,
> Georg
>
>
> -- 
> 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/groups/opt_out.
>  
>  
>

-- 
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/groups/opt_out.

Re: How do I know my plugin is actually released?

2013-03-03 Thread Georg Gruetter

All is well now! You've been a tremendous help, Kiyofumi! Thanks a lot for 
that.

Cheers,
Georg

On Sunday, 3 March 2013 11:44:58 UTC+1, Kiyofumi Kondoh wrote:
>
>
> Hi Georg. 
>
>  > {jenkins-plugin-info:pluginId=stashnotifier} 
>
> You must fix pluginId at wiki page. 
>
> your pom.xml artifactId is stashNotifier 
>
> Cheers, 
> Kiyofumi Kondoh 
>
>
>
> On 2013/03/03 3:30, Kiyofumi Kondoh wrote: 
> > 
> > Hi Georg. 
> > 
> >  > after the maven release I need to perform? 
> > No, almost wait on calmly. 
> > 
> > 
> >  > However, my Jenkins (1.500) still doesn't show the plugin 
> > Please check 
> > http://updates.jenkins-ci.org/update-center.json 
> > described at 
> > 
> > 
> https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Help%5C%21Mypluginisnotshowingupintheupdatecenter.
>  
>
> > 
> > 
> > Next, you click 'Check now' button or restart jenkins. 
> > 
> > 
> https://wiki.jenkins-ci.org/display/JENKINS/Plugins#Plugins-Usingtheinterface 
> >> Sometimes when you install, you will notice that the list of available 
> plugins is empty. 
> >  > If that is the case, from the Manage Plugins page, click on Check now 
> >  > (button available in the bottom right of the page) to forcefully 
> check for new updates. 
> >  > Once that is done, you should see the list of plugins. 
> > 
> > 
> >  > does the plugin wiki page <
> https://wiki.jenkins-ci.org/display/JENKINS/StashNotifier+Plugin> 
> >  > show any details with the jenkins-plugin-info macro. 
> > 
> > You should be write content at your plugin wiki page. 
> > But I think that jenkins-plugin-info macro reflect daily. 
> > 
> > 
> > 
> > Cheers, 
> > Kiyofumi Kondoh 
> > 
> > On 2013/03/03 2:03, Georg Gruetter wrote: 
> >> Hi Kiyofumi, 
> >> 
> >> thanks for bearing with me. I did upgrade to Maven 3.0.5 but the 
> problem 
> >> persists. I worked around that problem and manually performed the steps 
> >> release:prepare apparently omitted. After that, release:perform worked 
> just 
> >> fine and the plugin seems to be 
> >> deployed<
> http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/stashNotifier/1.0.2/>now.
>  
>
> >> 
> >> However, my Jenkins (1.500) still doesn't show the plugin nor does the 
> plugin 
> >> wiki page <
> https://wiki.jenkins-ci.org/display/JENKINS/StashNotifier+Plugin>show any 
> details with 
> >> the jenkins-plugin-info macro. Is there another step 
> >> after the maven release I need to perform? 
> >> 
> >> Cheers, 
> >> Georg 
> >> 
> >> On Friday, 1 March 2013 17:25:30 UTC+1, Kiyofumi Kondoh wrote: 
> >>> 
> >>> Hi Georg 
> >>> 
> >>> I try to use git-flow. 
> >>> Worked fine for me. 
> >>> 
> >>> tested repository 
> >>> https://github.com/kkkon/test_git-flow_maven-release-plugin 
> >>> 
> >>> git flow release start X.Y.Z 
> >>> mvn release:prepare 
> >>> mvn release:perform 
> >>> git flow release finish -n X.Y.Z 
> >>> 
> >>> 'git flow release finish' merge to develop and master branch. 
> >>> 
> >>> 
> >>> environment: 
>  S:\GITREPO\test_git-flow_maven-release-plugin>git flow version 
>  S:\msysgit\1.8.1.2_git-flow\bin\git-flow: line 118: init: command not 
> >>> found 
>  0.4.2-pre 
>  
>  S:\GITREPO\test_git-flow_maven-release-plugin>mvn -version 
>  Apache Maven 3.0.4 (r1232337; 2012-01-17 17:44:56+0900) 
>  Maven home: S:\Maven\3.0.4 
>  Java version: 1.6.0_37, vendor: Sun Microsystems Inc. 
>  Java home: D:\Java\x64\jdk1.6.0_37\jre 
>  Default locale: ja_JP, platform encoding: MS932 
>  OS name: "windows 7", version: "6.1", arch: "amd64", family: 
> "windows" 
>  S:\GITREPO\test_git-flow_maven-release-plugin> 
> >>> 
> >>> 
> >>> I'm sorry, distributionManagement doesn't need for your pom.xml 
> >>> 
> >>> distributionManagement seted by 
> >>>   org.jenkins-ci 
> >>>   jenkins 
> >>> It is grand-parent pom. 
> >>> 
> >>> 
> >>> Cheers, 
> >>> Kiyofumi Kondoh 
> >>> 
> >>> 
> >>> On 2013/03/01 21:41, Kiyofumi Kondoh wrote: 
>  Hi Georg 
>  
>    > I'm using the git-flow branching model. Might that be the 
> problem? 
>  You forgot run 'git flow release finish' at release 1.0 and 1.0.2 
>  
>    > Not sure I understand. Doesn't Maven first commit locally and 
> then 
> >>> push 
>    > that commit to the remote? If there's no local commit, I reckon 
> there 
> >>> can't 
>    > be anything that's pushed to a remote, right? 
>  
>  Sorry, you are right at release:prepare. 
>  But it different at release:perform 
>  
>  You read this? 
>  http://maven.apache.org/maven-release/maven-release-plugin/ 
>  You use maven 3.0.3. 
>  You try to upgrate to 3.0.4 or newer. 
>  
>  
>  Cheers 
>  Kiyofumi Konodh 
>  
>  On 2013/02/28 15:44, Georg Gruetter wrote: 
> > Hi Kiyofumi, 
> > 
> > On Thursday, 28 February 2013 06:14:02 UTC+1, Kiyofumi Kondoh wrote: 
> >> 
> >> Hi, Georg 
> >> 
> >> Sorry, your pom doesn't have distributio

Re: When should I mark a JIRA issue as "Resolved"?

2013-03-03 Thread Bruno P. Kinoshita

Usually I let the bot mark the issue as Resolved (with the [FIXED JENKINS-] 
commit log). 

Then when the plug-in is released and I see it either in the update center or 
in the twitter bot, I change the issue status to Closed with the message "Fixed 
in 9.99 version".

HTH, 

Bruno P. Kinoshita
http://kinoshita.eti.br
http://tupilabs.com


>
> From: Mark Waite 
>To: "jenkinsci-dev@googlegroups.com"  
>Sent: Saturday, March 2, 2013 9:55 AM
>Subject: When should I mark a JIRA issue as "Resolved"?
> 
>
>Is there a general policy or guideline related to when I should resolve an 
>issue which has been reported in JIRA?
>
>
>It seems there is a robot that resolves issues when certain text is detected 
>in git commit messages.  I think that indicates the general policy is to 
>resolve issues when the fix is submitted, not when the fix has been released 
>in an official build.
>
>
>I just reopened an issue because the fix seems to require updates to two 
>different plugins.  One of the plugins has been released with the fix, while 
>the other has not yet released a version which includes the fix.  I compiled a 
>local copy of the unreleased plugin, installed it, and confirmed that the 
>issue is resolved with the unreleased version of the plugin.
>
>
>Based on the robot behavior of resolving the issue when the change is 
>submitted, I think that means I should mark the issue as "resolved" since the 
>necessary changes are in the source code to fix the issue and users will 
>receive the fix with the next release of the plugin.  Is that the expectation?
>
>
>Thanks,
>Mark Waite
-- 
>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/groups/opt_out.
> 
> 
>
>
> 

-- 
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/groups/opt_out.

Re: How do I know my plugin is actually released?

2013-03-03 Thread Kiyofumi Kondoh

Hi Georg.

> {jenkins-plugin-info:pluginId=stashnotifier}

You must fix pluginId at wiki page.

your pom.xml artifactId is stashNotifier

Cheers,
Kiyofumi Kondoh

On 2013/03/03 3:30, Kiyofumi Kondoh wrote:

Hi Georg.

> after the maven release I need to perform?
No, almost wait on calmly.

> However, my Jenkins (1.500) still doesn't show the plugin
Please check
http://updates.jenkins-ci.org/update-center.json
described at

https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Help%5C%21Mypluginisnotshowingupintheupdatecenter.

Next, you click 'Check now' button or restart jenkins.

https://wiki.jenkins-ci.org/display/JENKINS/Plugins#Plugins-Usingtheinterface

Sometimes when you install, you will notice that the list of available plugins
is empty.

> If that is the case, from the Manage Plugins page, click on Check now
> (button available in the bottom right of the page) to forcefully check for
new updates.
> Once that is done, you should see the list of plugins.

> does the plugin wiki page

> show any details with the jenkins-plugin-info macro.

You should be write content at your plugin wiki page.
But I think that jenkins-plugin-info macro reflect daily.

Cheers,
Kiyofumi Kondoh

On 2013/03/03 2:03, Georg Gruetter wrote:

Hi Kiyofumi,

thanks for bearing with me. I did upgrade to Maven 3.0.5 but the problem
persists. I worked around that problem and manually performed the steps
release:prepare apparently omitted. After that, release:perform worked just
fine and the plugin seems to be
deployednow.

However, my Jenkins (1.500) still doesn't show the plugin nor does the plugin
wiki page
show any
details with
the jenkins-plugin-info macro. Is there another step
after the maven release I need to perform?

Cheers,
Georg

On Friday, 1 March 2013 17:25:30 UTC+1, Kiyofumi Kondoh wrote:

Hi Georg

I try to use git-flow.
Worked fine for me.

tested repository
https://github.com/kkkon/test_git-flow_maven-release-plugin

git flow release start X.Y.Z
mvn release:prepare
mvn release:perform
git flow release finish -n X.Y.Z

'git flow release finish' merge to develop and master branch.

environment:

S:\GITREPO\test_git-flow_maven-release-plugin>git flow version
S:\msysgit\1.8.1.2_git-flow\bin\git-flow: line 118: init: command not

found

0.4.2-pre

S:\GITREPO\test_git-flow_maven-release-plugin>mvn -version
Apache Maven 3.0.4 (r1232337; 2012-01-17 17:44:56+0900)
Maven home: S:\Maven\3.0.4
Java version: 1.6.0_37, vendor: Sun Microsystems Inc.
Java home: D:\Java\x64\jdk1.6.0_37\jre
Default locale: ja_JP, platform encoding: MS932
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
S:\GITREPO\test_git-flow_maven-release-plugin>

I'm sorry, distributionManagement doesn't need for your pom.xml

distributionManagement seted by
org.jenkins-ci
jenkins
It is grand-parent pom.

Cheers,
Kiyofumi Kondoh

On 2013/03/01 21:41, Kiyofumi Kondoh wrote:

Hi Georg

> I'm using the git-flow branching model. Might that be the problem?
You forgot run 'git flow release finish' at release 1.0 and 1.0.2

> Not sure I understand. Doesn't Maven first commit locally and then

push

> that commit to the remote? If there's no local commit, I reckon there

can't

> be anything that's pushed to a remote, right?

Sorry, you are right at release:prepare.
But it different at release:perform

You read this?
http://maven.apache.org/maven-release/maven-release-plugin/
You use maven 3.0.3.
You try to upgrate to 3.0.4 or newer.

Cheers
Kiyofumi Konodh

On 2013/02/28 15:44, Georg Gruetter wrote:

Hi Kiyofumi,

On Thursday, 28 February 2013 06:14:02 UTC+1, Kiyofumi Kondoh wrote:

Hi, Georg

Sorry, your pom doesn't have distributionManagement at github

https://github.com/jenkinsci/stashnotifier-plugin/blob/develop/pom.xml

https://github.com/jenkinsci/stashnotifier-plugin/blob/master/pom.xml

Actually it does, just not on the develop or master branch but on the
corresponding release branch:

https://github.com/jenkinsci/stashnotifier-plugin/blob/release/1.0.2/pom.xml

I'm using the git-flow branching model. Might that be the problem?

maven-release-plugin use scm repogitory, not your local git

repogitory.

Not sure I understand. Doesn't Maven first commit locally and then push
that commit to the remote? If there's no local commit, I reckon there

can't

be anything that's pushed to a remote, right?

you should read this

http://maven.apache.org/maven-release/maven-release-plugin/examples/prepare-release.html

and
mvn -DdryRun=true release:prepare release:perform
check to release phase.

That's good advice, I'll do that before I release next.

There is other option etc.

http://maven.apache.org/maven-release/maven-release-plugin/prepare-m

buildhive

jenkins with vss

How to determine which revision was built with a build?

RE: Jenkins and MKS inegration

Wiki page not updating after edit

Re: mvn release does not work, only publishes SNAPSHOT releases

Re: How do I know my plugin is actually released?

Re: When should I mark a JIRA issue as "Resolved"?

Re: How do I know my plugin is actually released?

9 matches

Site Navigation

Mail list logo

Footer information