Re: INFRA ci.jenkins.io

Hi Gavin, Thanks for the tip - certainly better then committing random edits to re-trigger the builds. Kind regards, Paul > On 15 Oct 2019, at 17:35, Gavin wrote: > > For now the easiest solution is to close the pr. Wait 30 secs and reopen it > > On Tue., Oct. 15, 2019, 3:48 a.m. pallen,

Re: 502 proxy error on ci.jenkins.io

Thanks - It seems to be working now. > On 2 Oct 2019, at 10:24, Olblak wrote: > > As you can see on this status page, there is definitely something wrong, I > start looking at it > > --- > -> gpg --keyserver keys.gnupg.net --recv-key 52210D3D > --- > > > > > On Wed, Oct 2, 2019, at 10:37 AM,

Re: Failed build.

Thanks - I submitted another change and it seems to be back to normal. > On 25 Oct 2018, at 13:41, Jesse Glick wrote: > > On Thu, Oct 25, 2018 at 4:57 AM pallen wrote: >> Possibly one for infrastructure, but I can't post to that group. > > You can always file a ticket in the `INFRA` project.

Re: Warning during multi-branch Indexing

n Wed, Oct 4, 2017 at 7:06 AM, Paul Allen <pal...@perforce.com<mailto:pal...@perforce.com>> wrote: I'm still using workflow-aggregator:jar:2.5 I strongly advise against using `workflow-aggregator` as a `test`-scoped dependency. -- You received this message because you are subscribed to the

Re: Warning during multi-branch Indexing

Thank you. I'm still using workflow-aggregator:jar:2.5 and that was using pipeline-milestone-step 1.3. During development I tend the run up the plugin with 'hpi:run' rather than installing it in a running Jenkins. On 4 Oct 2017, at 11:29, Stephen Connolly

Re: Global Pipeline Libraries support for p4-plugin

Thank you :-) I had implemented SCMSource for MultiBranch, but only the retrieve method for observer (2.0). I can't find any 2.0 methods in the documentation link you sent - is this out-of-date? Think I found the method in the source... /** * SPI: Looks up a specific revision based on some

Re: P4 plugin - Multibranch PRs and Branches

BTW I have not implemented SCMNavigator, is this required? On 12 Jun 2017, at 14:45, Paul Allen <pal...@perforce.com<mailto:pal...@perforce.com>> wrote: Hi Stephen, (1) Thank you - so if I understand correctly, if retrieve no longer finds it observer is not called and it appears

Re: Jelly to Groovy

Perfect; that fixed it. Thank you, Paul > On 21 Apr 2017, at 16:53, Robert Sandell <rsand...@cloudbees.com> wrote: > > Yes, instance is not always available, so the simplest thing to do would be: > instance?.isSsl() > > /B > > On Fri, Apr 21, 2017 at 5:25 PM, P

Re: Jelly to Groovy

Hi Robert, Thanks for the include details for the credentials, that worked. Unfortunately the checked instance.isSsl() failed with: Caused by: java.lang.NullPointerException: Cannot invoke method isSsl() on null object Kind regards, Paul > On 21 Apr 2017, at 15:19, Robert Sandell

Re: Serialization of TaskListener

Thanks for the comments on GitHub, I have switch over to use MasterToSlaveCallable. The code seems to work well and my tests are passing, also tested it manually on remote slaves with no issue. P4Groovy is just a wrapper for the Strings/Booleans that describe the Credentials and Workspace

Re: Serialization of TaskListener

Hi Jesse, I was passing TaskListener to allow logging/reporting in the Console Output. Is there a static method I can call instead? My code gets invoked by FileCallable<>: T invoke(File f, VirtualChannel channel) throws IOException, InterruptedException; Alternatively I might be able

Re: Plugin mvn release:perform

Thanks. I think that worked. Strangely the page below references maven.jenkins-ci.org for the credential. I too had to use this address or I got a 401. https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/p4/1.4.6/p4-1.4.6.hpi maven.jenkins-ci.org ... ...

Groovy DSL arguments

Hi Devs, Jesse, I have written two DSL functions ‘p4fetch’ and ‘p4save’ (extending AbstractStepImpl). The ‘p4fetch’ DSL returns a Map object which I can print out and modify. e.g: def client = p4fetch id: 'test-001', type: 'client' echo "client: ${client}" def host =

Re: checkout scm and Jenkinsfile

Thanks, I’ll keep an eye on JENKINS-33273. Perhaps looking for @script is a short term fix after all. Then I can limit the checkout to just the Jenkinsfile. > On 1 Jun 2016, at 17:52, Jesse Glick <jgl...@cloudbees.com> wrote: > > On Wed, Jun 1, 2016 at 12:46 PM,

Re: checkout scm and Jenkinsfile

In the SCM configuration I specify what path(s) to fetch from the SCM e.g. //depot/projA/src/... The root directory of ‘src’ contains the ‘Jenkinsfile' and say for arguments sake a game engine of 100K files (500 GB of space). Currently I end up syncing 500GB twice once in 'projA@script/' and

Re: Cleanup on 'Delete Project' (deleting a Jenkins Job)

Thank you. > On 15 Jan 2016, at 18:32, Daniel Beck wrote: > > > On 15.01.2016, at 17:50, pallen wrote: > >> How do you hook into the Delete Project event when a Jenkins Job is deleted? > >

Re: Unable to release P4 plugin

nt.java:52) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543) at java.lang.Thread.run(Thread.java:679) Paul > On 6 Jan 2016, at 11:46, Paul Allen <pal...@perforce.com> wrote: > > Hi Vi

Re: Unable to release P4 plugin

Hi Victor, No my password is unchanged (been using the same password for may years). However I am unable to login to: https://repo.jenkins-ci.org/webapp/#/login I tried the 'Forgot Password' link, but get no email? My user name is 'p4paul' are you able to verify my account exists? Kind

Re: Unable to release P4 plugin

Thank you! P4 has now successfully been deployed. Paul > On 6 Jan 2016, at 16:48, Baptiste Mathus wrote: > > BTW, for those wondering it's been fixed some minutes after James' email. > > So releasing should be possible now. > > Thanks Arnaud! > > Le 6 janv. 2016 2:01 PM,

Re: Using Environment variables in Workflow

Hi Jesse, Yes, it extends SCMStep… https://github.com/jenkinsci/p4-plugin/blob/master/src/main/java/org/jenkinsci/plugins/p4/workflow/P4Step.java#LC24 I added two break points in SCM.buildEnvVars and my own buildEnvVars and neither get hit during a Workflow build. I’ll do a bit of hacking,

Re: Missing source or broken link?

Hi Emeric, Thank you for the link. Kind regards, Paul On 12 Aug 2015, at 09:58, evernat ever...@free.fr wrote: I do not know why the link is broken in the wiki page. But the source seems to be at: https://github.com/jenkinsci/jenkins.py and some docs are at:

Re: Request for new p4workflow plugin

content, I noticed url (which may be deliberate?) and name. On 10.08.2015, at 18:45, Paul Allen pal...@perforce.com wrote: Hi Daniel, I wanted to keep the ‘p4’ plugin at Jenkins 1.568 to maintain backwards compatibility for non Workflow users. To implement ‘SimpleBuildStep’ I would

Re: Request for new p4workflow plugin

Ok, so adding '@Extension(optional = true)' on DescriptorImpl resolved the load issues. No idea on the cause of the build error for 1.565.3, but at least 1.580.1 mostly works. On 11 Aug 2015, at 15:50, Paul Allen pal...@perforce.com wrote: Well nothing in the core part of ‘p4' broke

Re: Request for new p4workflow plugin

Well nothing in the core part of ‘p4' broke with 1.580.1, just some of the DSL support. Looks like I need 1.596.1 for that to work. Although with 1.580.1 I do get some errors on startup (see below), is there an annotation I can add to suppress load errors (some sort of optional=true) Aug

Re: Request for new p4workflow plugin

is this a separate plugin? (Also, some pom.xml metadata is still for the P4 Plugin) Daniel On 10.08.2015, at 17:13, Paul Allen pal...@perforce.com wrote: Hi Guys, Please can I create a new plugin to extend the ‘p4’ for DSL and extended workflow support. Plugin Name: p4workflow

Request for new p4workflow plugin

Hi Guys, Please can I create a new plugin to extend the ‘p4’ for DSL and extended workflow support. Plugin Name:p4workflow GitHub User:p4paul Initial checkin: https://github.com/p4paul/p4workflow Kind regards, Paul

Re: Remoting support from inside AbstractScmTagAction

Perhaps I should be using TaskThread? My TaggingTask extends AbstractTask and implements FileCallableBoolean. It seems that TaskListener is built into TaskThread. (example here:

Re: How do I add my 'p4' plugin to Enterprise/Cloudbees

center lines then as 1.568 is not one of the lines we support On 27 April 2015 at 15:36, Paul Allen pal...@perforce.com wrote: I have recently added support back to Jenkins 1.568 (1.2.2-SNAPSHOT). If I need to make 'matrix-project’ optional do let me know. Kind regards, Paul On 27 Apr

Re: How do I add my 'p4' plugin to Enterprise/Cloudbees

based on the version in the ?jenkins_version= parameter on the request URL. So this will not show up if using CJE 14.05. I see p4 when ?jenkins_version=1.580.1.1 On Wednesday, April 29, 2015, Paul Allen pal...@perforce.com wrote: Thanks for the replies, but I guess I don’t understand

Re: How do I add my 'p4' plugin to Enterprise/Cloudbees

Thanks. Lets hope the sanity tests pass. Will this require an update to the white list every time I release a new version? On 29 Apr 2015, at 13:21, Jesse Glick jgl...@cloudbees.com wrote: On Mon, Apr 27, 2015 at 5:52 AM, pallen pal...@perforce.com wrote: I have just started to use the

Re: How do I add my 'p4' plugin to Enterprise/Cloudbees

community. From CB side it will be really effectively to document this on some of their documentation page. On Apr 29, 2015, at 16:14, Paul Allen pal...@perforce.com wrote: Thanks. Lets hope the sanity tests pass. Will this require an update to the white list every time I release a new

Re: How do I add my 'p4' plugin to Enterprise/Cloudbees

I have recently added support back to Jenkins 1.568 (1.2.2-SNAPSHOT). If I need to make 'matrix-project’ optional do let me know. Kind regards, Paul On 27 Apr 2015, at 15:08, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Ah, ok, you did. Paul: I'm seeing p4 in our update

Re: How do I add my 'p4' plugin to Enterprise/Cloudbees

then as 1.568 is not one of the lines we support On 27 April 2015 at 15:36, Paul Allen pal...@perforce.com wrote: I have recently added support back to Jenkins 1.568 (1.2.2-SNAPSHOT). If I need to make 'matrix-project’ optional do let me know. Kind regards, Paul On 27 Apr 2015, at 15:08

Re: How do I add my 'p4' plugin to Enterprise/Cloudbees

The current release supports only 1.580.3 and newer. On 27 Apr 2015, at 16:00, Paul Allen pal...@perforce.com wrote: Just like Jesse’s ‘Mercurial' plugin I support back to 1.568 (later version are ok). On 27 Apr 2015, at 15:46, Stephen Connolly stephen.alan.conno...@gmail.com wrote

Re: Unfinished implementation in SCM class for buildEnvVars method

, Feb 6, 2015 at 10:59 AM, Paul Allen pal...@perforce.com wrote: ERROR: P4: Run not instance of AbstractBuild. Sounds like an error coming from your own code. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from

Re: Unfinished implementation in SCM class for buildEnvVars method

that will become apparent as I experiment. Kind regards, Paul On 5 Feb 2015, at 16:11, Jesse Glick jgl...@cloudbees.com wrote: On Tue, Feb 3, 2015 at 12:10 PM, Paul Allen pal...@perforce.com wrote: How do I get a job from a run? Previously AbstractBuild had a getProject() method. Use

Re: Unfinished implementation in SCM class for buildEnvVars method

, Jesse Glick jgl...@cloudbees.com wrote: On Fri, Feb 6, 2015 at 10:44 AM, Paul Allen pal...@perforce.com wrote: How would I add support for 'p4:' syntax instead (like the 'git:' example) instead of the 'scm: [$class: 'PerforceScm']' syntax? For that you would need to create a custom subclass

Re: Unfinished implementation in SCM class for buildEnvVars method

How would I add support for 'p4:' syntax instead (like the 'git:' example) instead of the 'scm: [$class: 'PerforceScm']' syntax? On 6 Feb 2015, at 15:08, Jesse Glick jgl...@cloudbees.com wrote: On Fri, Feb 6, 2015 at 9:27 AM, Paul Allen pal...@perforce.com wrote: I have been following

Re: Deploying to Jenkins Artifactory

Hi Vincent, Thanks, I had completely forgotten to look at the version string and add -SNAPSHOT (its an ugly manual process I do once a year). Kind regards, Paul On 4 Feb 2015, at 19:40, Vincent Latombe vincent.lato...@gmail.com wrote: Hi, as mentioned in the error message, you are

Re: Unfinished implementation in SCM class for buildEnvVars method

Hi Guys, Sorry if this is documented, but I have more questions... - How do I get a job from a run? Previously AbstractBuild had a getProject() method. - MatrixBuild/MatrixConfigurations don't seem to be updated? - Notify/Publish seem to use AbstractBuild - RunListener seems half way?

Re: Release location

:21 schrieb Paul Allen pal...@perforce.com: Has the release process changed? This has worked for the last 17 releases, but I now can't find my release on: http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/p4/ It seems to have moved to snapshots? http://repo.jenkins-ci.org

Re: Missing getScm() method in the new Run/Job update.

Thanks for the comments; I have switched the code back to accessing the objects from the SCM and cleaned up the remaining references to AbstractBuild. Kind regards, Paul On 7 Aug 2014, at 15:05, Jesse Glick jgl...@cloudbees.com wrote: On Thu, Aug 7, 2014 at 6:10 AM, pallen

p4 plugin not showing in update centre

It seems the p4-plugin project is not showing up in the update centre? I forgot to add the wiki page prior to release, however the POM did have the correct URL. I have since added the actual wiki page to match the POM, do I need to re-release even though there were no changes?

Re: p4 plugin not showing in update centre

GMT+04:00 Rob Petti rob.pe...@gmail.com: Have you released it already? If so, it takes up to 6 hours to show up in the update center. If not, then that would be why. On Mon, Jul 7, 2014 at 8:30 AM, Paul Allen pal...@perforce.com wrote: It seems the p4-plugin project is not showing up

Re: p4 plugin not showing in update centre

, Jul 7, 2014 at 10:27 AM, Rob Petti rob.pe...@gmail.com wrote: Wiki pages aren't required for plugins to show up on the updatecenter. On Mon, Jul 7, 2014 at 9:52 AM, Paul Allen pal...@perforce.com wrote: Sure I can change it to a display name of P4 Plugin. I tried the release over the weekend

Re: New plugin Perforce

Ulli, Any chance you could create this for me? Paul On 3 Jul 2014, at 11:06, Stephen Connolly stephen.alan.conno...@gmail.com wrote: I'm having issues with my IRC client since I switched machines... somebody else might be able to help On 3 July 2014 10:18, Paul Allen pal

Re: New plugin Perforce

the two plugins together. Paul On 3 Jul 2014, at 16:37, Rob Petti rob.pe...@gmail.com wrote: I just tried to fork it, but jenkins-admin apparently died in the process. On Thu, Jul 3, 2014 at 9:17 AM, Paul Allen pal...@perforce.com wrote: Ulli, Any chance you could create this for me

Re: New plugin Perforce

. On Thu, Jul 3, 2014 at 9:57 AM, Paul Allen pal...@perforce.com wrote: Hi Rob, Was that the 'jenkinsci/perforce-plugin' you were trying to fork? I was going to attempt a release under a new 'jenkinsci/p4-plugin' to avoid the migration issues and use of the beta update centre. If I can

Re: New plugin Perforce

package name is one of: * org.jenkinsci.plugins.X; or * jenkins.plugins.X; or * com.mycompany.jenkins.X (if you want to credit a company providing the vast bulk of the contribution *and* intending to maintain the plugin going foward) HTH On 30 June 2014 11:20, Paul Allen pal

Re: New plugin Perforce

be org.jenkinsci.plugins.p4 or similar? Kind regards, Paul 2014-06-27 0:11 GMT+04:00 Paul Allen pal...@perforce.com: Hi Oleg, On 26 Jun 2014, at 15:53, Oleg Nenashev o.v.nenas...@gmail.com wrote: My managers don't want to invest into such migration without a middle-term advantage. They think

Re: New plugin Perforce

Hi Guys, Sorry I missed your earlier emails; it got buried in hundreds of Jenkins dev emails. I'm in the process of moving the project out of the Perforce Workshop into GitHub. When I'm done you should be able to view the code under: https://github.com/p4paul/p4-jenkins Oleg: I don't

Re: New plugin Perforce

Hi Oleg, On 26 Jun 2014, at 15:53, Oleg Nenashev o.v.nenas...@gmail.com wrote: My managers don't want to invest into such migration without a middle-term advantage. They think that Perforce guys should be responsible for the compatibility since we pay you money ;) I definitely don't want

Re: New plugin Perforce

will need help to deploy this (whether under the beta update centre, or as a branch). Alternatively, I could use a new 'p4' name space, but again I would appreciate help with deploying this. Kind regards, Paul On 21 May 2014, at 10:06, Paul Allen pal...@perforce.com wrote: Hi Oleg, Sorry for any

Re: New plugin Perforce

the official 2.0 release. Or if we discover that feature parity is unattainable, we can rename the new version to another name and release it as a separate plugin. On 04/18/2014 02:33 AM, Paul Allen wrote: Hi Rob, The refactoring effort would be so wide spread there would

Re: New plugin Perforce

will get this 2.0 beta versions. When 2.0 is in feature parity, we can have the official 2.0 release. Or if we discover that feature parity is unattainable, we can rename the new version to another name and release it as a separate plugin. On 04/18/2014 02:33 AM, Paul Allen wrote: Hi

Re: New plugin Perforce

Hi Niksan, The Jenkins plugin had popped up on Perforce's radar a few times; often for performance issues. With our new Swarm tool we wanted a better Continuous Build experience and needed to update the plugin. Starting that process we identified a few issues: 1. Maintainability - It's

Re: New plugin Perforce

Hi Niksan, On 23 Apr 2014, at 15:48, Niksan sumot...@googlemail.com wrote: Point 3, this is the big one for me, I'm an advocate for using a command line wrapper in regards to Perforce, this is with experience of using the .NET API and the fact the APIs are closed source so you're at mercy to

Re: New plugin Perforce

Hi Steve, Thanks for your reply, I have added comments below... [Steve RE: Credentials] The new plugin extends Jenkins Credentials into two new types. Perforce Password credential and Perforce Ticket credential; these both support SSL and P4TRUST finger prints. I did look at the password

Re: New plugin Perforce

this 2.0 beta versions. When 2.0 is in feature parity, we can have the official 2.0 release. Or if we discover that feature parity is unattainable, we can rename the new version to another name and release it as a separate plugin. On 04/18/2014 02:33 AM, Paul Allen wrote: Hi Rob

Re: New plugin Perforce

The existing 'perforce' plugin is used by many of our customers and I was concerned that effectively replacing it with the new plugin may upset some users. Whilst the new plugin provides all the basic SCM functions, it is not yet as feature rich. We plan to add features over the next few

Re: New plugin Perforce

I have been discussing the plugin for sometime over email. I'll CC Rob and the others... Paul On 17 Apr 2014, at 16:59, Jesse Glick jgl...@cloudbees.com wrote: On Thu, Apr 17, 2014 at 11:51 AM, Paul Allen pal...@perforce.com wrote: Whilst the new plugin provides all the basic SCM functions