Re: Not able to release new version of plugin

[Irfan Sayed]

Thanks.
In the effective POM, i have following:

 

  java.net-m2-repository
  http://maven.jenkins-ci.org/content/repositories/releases/


  maven.jenkins-ci.org
  http://maven.jenkins-ci.org:8081/content/repositories/snapshots



  github-pages
  
gitsite:g...@github.com/jenkinsci/maven-site.git:plugin-parent/sinatra-chef-builder


  

in snapshot repository, there is a port 8081
but in release repo it is not.
please let me know

regards,



On Thu, Jan 5, 2017 at 6:46 AM, Daniel Beck  wrote:

>
> > On 05.01.2017, at 15:15, Irfan Sayed  wrote:
> >
> > still the same error
>
> Unsurprising given that this still referenced the host name that has been
> shut down.
>
> --
> 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.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/6EF8E60C-351D-43F5-B873-B201E5F32FC9%40beckweb.net.
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CACGLCJaqJQjO-8ctOya5-U5kMALULRqY2fiadqiRg5FrB07tqA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: distributed build behavior, java.io.* classes, and security

[Robert St. John]

Thanks for your reply.  I discovered by trial and error today what you said
about using FilePath.  I changed all my java.io usage to FilePath and used
a MasterToSlaveFileCallable subclass to accomplish my goal.  What was not
intuitive to me was that my Builder code is executed on master, while the
process I invoked using the launcher ran on the slave.  I assumed that all
the instructions of my Builder were executing on the slave.  I ran into a
problem when code in my Builder needed to use a java.io.File object in the
Builder to reference the output file of the process I launched with the
launcher, and so the java.io.File did not exist as far as the Builder was
concerned.  Am I interpreting what I'm seeing correctly?

Regarding what you said about secrets, I ended up passing a decrypted
java.security.Key instance through a FileCallable to the slave.  Would that
ever be written to disk?  I could alternatively look up the private key
from within the FlleCallable, but I believe that would result in the
Credentials plugin sending the key store password secret over the wire
anyway.  What should I do to maximize the security and minimize assumptions
about the way my Builder is run?

Thanks.

Robert

On Thu, Jan 5, 2017 at 3:12 PM, Jesse Glick  wrote:

> On Tue, Dec 27, 2016 at 12:54 PM, Robert St. John 
> wrote:
> > I am using the Credentials
> > plugin to load a keystore from a StandardCertificateCredential, which as
> I
> > understand ultimately uses FilePath to load the keystore from the master
> > node.
>
> Yes, existing Jenkins code does send secrets over the wire to agents,
> if they are being used for a build run on that agent. In general this
> is unavoidable; in many cases the secrets will in fact wind up on disk
> on the agent for the duration of the build, or be accessible from
> `/proc`.
>
> If you wish to protect secrets from access by other builds, you have
> no choice but to ensure either that each build runs on a “one-shot”
> agent running in a container/VM (the Docker cloud model); or that each
> build is somehow required to run all its build steps inside a fresh
> container/VM even when the agent is reused (the Docker Pipeline model,
> with restricted scripts).
>
> And yes you must use `FilePath` for all file operations relating to
> workspaces. You can use `act` to perform a chunk of work remotely in
> the interests of efficiency.
>
> --
> 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/xdyw9Jo4Fug/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/CANfRfr3gqj2OuSNdKeH5MNRrhACFpyLi-N5%2BLBHMeNdvj272rQ%
> 40mail.gmail.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAEoDabuM2X6JnJh42LJfrv%2B55RzqOE%2B2U-4EMEW32GtXPVciJw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Retrieving a list of Pipeline jobs

[Emory Penney]

Thanks for the suggestions!  Also, the historical background makes this
much clearer.  Neither of those classes have getTrigger() implemented, any
tips for how to get build triggers from Job.class or WorkflowJob.class?

On Thu, Jan 5, 2017 at 2:19 PM, Jesse Glick  wrote:

> On Thu, Jan 5, 2017 at 3:45 PM, Emory Penney 
> wrote:
> > I've noticed that
> >
> > Jenkins.getInstance().jenkinsInstance.getAllItems(
> AbstractProject.class);
> >
> > doesn't seem to get me a list of Pipelines jobs.  I'm sure I need to use
> a
> > different class but I'm unclear which one.
>
> `Job.class` to get anything, or `WorkflowJob.class` to get Pipeline only.
>
> https://github.com/jenkinsci/pipeline-plugin/blob/master/
> DEVGUIDE.md#historical-background
>
> Currently there is not an official (i.e., API plugin) marker interface
> for `Job` subtypes that would correspond to the
> `FlowExecutionOwner.Executable` marker interface for `Run` subtypes,
> though I have been thinking about adding one as it would be useful on
> occasion.
>
> --
> 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/PKbpT-84ie4/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/CANfRfr1V88O%3DB%2BotL%2BZNRutpGyTfjbdBQnUvyrjykxafJp
> %2BY_g%40mail.gmail.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CABch0G0RFA2skk3od%2BYLBpzU-HYmsMSYbS4ARR2N6KCb4xJUfw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Retrieving a list of Pipeline jobs

[Jesse Glick]

On Thu, Jan 5, 2017 at 3:45 PM, Emory Penney  wrote:
> I've noticed that
>
> Jenkins.getInstance().jenkinsInstance.getAllItems(AbstractProject.class);
>
> doesn't seem to get me a list of Pipelines jobs.  I'm sure I need to use a
> different class but I'm unclear which one.

`Job.class` to get anything, or `WorkflowJob.class` to get Pipeline only.

https://github.com/jenkinsci/pipeline-plugin/blob/master/DEVGUIDE.md#historical-background

Currently there is not an official (i.e., API plugin) marker interface
for `Job` subtypes that would correspond to the
`FlowExecutionOwner.Executable` marker interface for `Run` subtypes,
though I have been thinking about adding one as it would be useful on
occasion.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1V88O%3DB%2BotL%2BZNRutpGyTfjbdBQnUvyrjykxafJp%2BY_g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: distributed build behavior, java.io.* classes, and security

[Jesse Glick]

On Tue, Dec 27, 2016 at 12:54 PM, Robert St. John  wrote:
> I am using the Credentials
> plugin to load a keystore from a StandardCertificateCredential, which as I
> understand ultimately uses FilePath to load the keystore from the master
> node.

Yes, existing Jenkins code does send secrets over the wire to agents,
if they are being used for a build run on that agent. In general this
is unavoidable; in many cases the secrets will in fact wind up on disk
on the agent for the duration of the build, or be accessible from
`/proc`.

If you wish to protect secrets from access by other builds, you have
no choice but to ensure either that each build runs on a “one-shot”
agent running in a container/VM (the Docker cloud model); or that each
build is somehow required to run all its build steps inside a fresh
container/VM even when the agent is reused (the Docker Pipeline model,
with restricted scripts).

And yes you must use `FilePath` for all file operations relating to
workspaces. You can use `act` to perform a chunk of work remotely in
the interests of efficiency.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3gqj2OuSNdKeH5MNRrhACFpyLi-N5%2BLBHMeNdvj272rQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Plugin that uses Acceptance Test Harness tests

[Jesse Glick]

On Thu, Dec 22, 2016 at 5:44 PM, Ullrich Hafner
 wrote:
> I also do such plug-in integration tests before a release of my
> plugins, but I run them from the ATH.

There is a standing conflict between keeping all tests in one place,
vs. all in plugin repositories. Both have their pros and cons. As a
general rule, we try to reserve ATH for a small subset of tests which
require heavy GUI interaction and validate Jenkins features at a high
level, possibly spanning multiple plugins/components; as opposed to
`JenkinsRule`-based tests (and true unit tests), which are expected to
be more numerous and cover finer-grained details. So back to your
reasoning

> particularly in cases where there is an interaction with an external system 
> that may be difficult to mock

This is precisely why I have extracted the Docker fixture system to a
standalone library usable from `JenkinsRule`-based tests:

https://issues.jenkins-ci.org/browse/JENKINS-40808

> So that we see if Jenkins core breaks something related to your
> plugin.

Presumably `plugin-compat-tester` would now catch such problems, if
someone were to include this plugin in the list of those tested.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1sQgkuHCwk9z%3DG1SUgszBoT%3DV6-nFVAs1c26xuKmbCuQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: How can a plugin save output when running in pipeline

[Jesse Glick]

On Mon, Dec 26, 2016 at 4:13 PM, Christian McHugh
 wrote:
> I'm a bit stuck on the conversion of SimpleBuildStep to full step needed to
> have the pipeline syntax be able to return output to be saved into a
> variable.
> As I'm not a jenkins framework expert by any means, would anyone be able to
> provide any additional assistance on the mentioned step conversion?

Does 
https://github.com/jenkinsci/workflow-basic-steps-plugin/blob/32c7e74953c98acb2703f4130b48cd93dabcf65f/src/main/java/org/jenkinsci/plugins/workflow/steps/ReadFileStep.java#L40-L105
help?

https://github.com/jenkinsci/workflow-step-api-plugin/blob/master/README.md#creating-a-basic-synchronous-step

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1MULaLcjNP%2B1TatoJ9i%2BX2JO8fxP34PSyqsoQu4DMV4g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

RE: Can't create a compatibility alias for a credentials BaseStandardCredentials subclass and a Messages class

['Claudiu Guiman' via Jenkins Developers]

Hi,
I think I figured it out. The credential plugin it’s using any of the XStream 
instances from Jenkins and it’s using the DEFAULT_XSTREAM member from XmlFile.
Shouldn’t getConfigFile create a new XmlFile by providing the XSTREAM2 alias 
from Jenkins?
https://github.com/jenkinsci/credentials-plugin/blob/master/src/main/java/com/cloudbees/plugins/credentials/SystemCredentialsProvider.java#L124


From: 'Claudiu Guiman' via Jenkins Developers 
[mailto:jenkinsci-dev@googlegroups.com]
Sent: Thursday, January 5, 2017 10:33
To: jenkinsci-dev@googlegroups.com
Subject: Can't create a compatibility alias for a credentials 
BaseStandardCredentials subclass and a Messages class

Hi,
I have to change the package names and I’m trying to migrate the data from the 
old class.
To accomplish this I’ve tried adding a compatibility alias during 
initialization and it works for other classes I had to rename, but not for the 
credentials class and Messages (the auto-generated class from 
Messages.properties resource file)
The code looks something like this:
@Initializer(before = InitMilestone.PLUGINS_STARTED)
public static void addAliases() {

Jenkins.XSTREAM2.addCompatibilityAlias("com.microsoft.azure.util.AzureCredentials",
 AzureCredentials.class); //doesn’t work

Jenkins.XSTREAM2.addCompatibilityAlias("com.microsoft.azure.AzureVMCloud", 
AzureVMCloud.class); //works

Jenkins.XSTREAM2.addCompatibilityAlias("com.microsoft.azure.AzureVMAgent", 
AzureVMAgent.class); //works

Jenkins.XSTREAM2.addCompatibilityAlias("com.microsoft.azure.Messages", 
Messages.class); //doesn’t work
}

I’ve also tried using the XSTREAM2 instance from other classes like Items and 
Run, but Jenkins it’s still not able to get rid of the Jenkins migration errors:
com.cloudbees.plugins.credentials.SystemCredentialsProvider

Manage Credentials

CannotResolveClassException: com.microsoft.azure.util.AzureCredentials,

com.microsoft.azure.vmagent.AzureVMAgent

test1234-983ce0

ConversionException: Cannot load java class com.microsoft.azure.Messages  
Debugging information  message : Cannot load java class 
com.microsoft.azure.Messages class : java.lang.Class required-type : 
java.lang.Class converter-type : 
com.thoughtworks.xstream.converters.SingleValueConverterWrapper 
wrapped-converter : 
com.thoughtworks.xstream.converters.extended.JavaClassConverter path : 
/com.microsoft.azure.AzureVMAgent/cleanUpReason/holder/owner line number : 38 
---


Where should I add my alias?

Thank you,
Claudiu Guiman
--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CY1PR0301MB1660B856E7C48813FE97CDBBD7600%40CY1PR0301MB1660.namprd03.prod.outlook.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CY1PR0301MB1660B8B87AFF6862595344C0D7600%40CY1PR0301MB1660.namprd03.prod.outlook.com.
For more options, visit https://groups.google.com/d/optout.

Retrieving a list of Pipeline jobs

[Emory Penney]

Hi,

Sorry for the noob question, I'm sure this is answered somewhere in the 
documentation I'm just completely unable to find it...

I've noticed that

Jenkins.getInstance().jenkinsInstance.getAllItems(AbstractProject.class);


doesn't seem to get me a list of Pipelines jobs.  I'm sure I need to use a 
different class but I'm unclear which one.  Or is there a different 
preferred method for getting a list of pipeline jobs?

Thanks in advance 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/6bf2465f-e322-405e-846d-9d8d84ed156d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Experiment] Reviewers Team

[Oliver Gondža]

On 2017-01-05 17:01, Daniel Beck wrote:



On 10.08.2016, at 08:42, James Dumay  wrote:

All of the blueocean-plugin PRs mention the reviewers team... so If you are 
looking to get involved in Blue Ocean reviewing is a great place to start!


FTR I asked that this practice be stopped a few weeks ago, as it increased the 
notification traffic a lot, and the BO developers generally seem to have no 
problem finding reviewers for their changes.


Amen.
--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/c7c7abd2-34ff-7c3b-f787-fbaabe31aa35%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

GSOC 17

[shubham sharma]

Hello, I am looking forward to participate in GSOC'17 & am new to open 
source developmemt. Please can anyone help getting started ?

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/3a6688dd-5938-4d23-a7e4-a04ba0de2f04%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Can't create a compatibility alias for a credentials BaseStandardCredentials subclass and a Messages class

['Claudiu Guiman' via Jenkins Developers]

Hi,
I have to change the package names and I'm trying to migrate the data from the 
old class.
To accomplish this I've tried adding a compatibility alias during 
initialization and it works for other classes I had to rename, but not for the 
credentials class and Messages (the auto-generated class from 
Messages.properties resource file)
The code looks something like this:
@Initializer(before = InitMilestone.PLUGINS_STARTED)
public static void addAliases() {

Jenkins.XSTREAM2.addCompatibilityAlias("com.microsoft.azure.util.AzureCredentials",
 AzureCredentials.class); //doesn't work

Jenkins.XSTREAM2.addCompatibilityAlias("com.microsoft.azure.AzureVMCloud", 
AzureVMCloud.class); //works

Jenkins.XSTREAM2.addCompatibilityAlias("com.microsoft.azure.AzureVMAgent", 
AzureVMAgent.class); //works

Jenkins.XSTREAM2.addCompatibilityAlias("com.microsoft.azure.Messages", 
Messages.class); //doesn't work
}

I've also tried using the XSTREAM2 instance from other classes like Items and 
Run, but Jenkins it's still not able to get rid of the Jenkins migration errors:

com.cloudbees.plugins.credentials.SystemCredentialsProvider

Manage Credentials

CannotResolveClassException: com.microsoft.azure.util.AzureCredentials,

com.microsoft.azure.vmagent.AzureVMAgent

test1234-983ce0

ConversionException: Cannot load java class com.microsoft.azure.Messages  
Debugging information  message : Cannot load java class 
com.microsoft.azure.Messages class : java.lang.Class required-type : 
java.lang.Class converter-type : 
com.thoughtworks.xstream.converters.SingleValueConverterWrapper 
wrapped-converter : 
com.thoughtworks.xstream.converters.extended.JavaClassConverter path : 
/com.microsoft.azure.AzureVMAgent/cleanUpReason/holder/owner line number : 38 
---


Where should I add my alias?

Thank you,
Claudiu Guiman

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CY1PR0301MB1660B856E7C48813FE97CDBBD7600%40CY1PR0301MB1660.namprd03.prod.outlook.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Experiment] Reviewers Team

[Daniel Beck]

> On 10.08.2016, at 08:42, James Dumay  wrote:
> 
> All of the blueocean-plugin PRs mention the reviewers team... so If you are 
> looking to get involved in Blue Ocean reviewing is a great place to start!

FTR I asked that this practice be stopped a few weeks ago, as it increased the 
notification traffic a lot, and the BO developers generally seem to have no 
problem finding reviewers for their changes.

Now @jenkinsci/code-reviewers should be back to be fairly low traffic and 
limited to PRs where someone really thinks reviews are needed:

https://github.com/pulls?utf8=%E2%9C%93=is%3Aopen+is%3Apr+team%3Ajenkinsci%2Fcode-reviewers

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/295C45E0-528F-4D27-81BE-1A89C3C94BBF%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: [Experiment] Reviewers Team

[Daniel Beck]

> On 05.01.2017, at 16:44, Jacob Larfors  wrote:
> 
> just checking that the @jenkinsci/code-reviewers group is still around

It's still around and configured to be visible.

However, you're not a member of the jenkinsci GitHub organization as you 
haven't accepted the invitation that was sent to you, and it seems teams and 
mentions are limited to org members.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/0F2FAE2D-55E2-4194-8571-55164CEE5286%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: [Experiment] Reviewers Team

[Jacob Larfors]

Hello,

just checking that the @jenkinsci/code-reviewers 
 group is still 
around? Doesnt seem to exist in GitHub anymore... at least I get a 404 
error not found

https://github.com/orgs/jenkinsci/teams/code-reviewers

I was hoping to get some feedback on a recent pull request 
here: https://github.com/jenkinsci/klocwork-plugin/pull/20

Thanks,
Jacob

On Wednesday, 10 August 2016 09:42:26 UTC+3, James Dumay wrote:
>
> All of the blueocean-plugin PRs mention the reviewers team... so If you 
> are looking to get involved in Blue Ocean reviewing is a great place to 
> start!
>
> On Wednesday, August 10, 2016 at 4:22:56 AM UTC+10, Baptiste Mathus wrote:
>>
>> Small bump: reminder this list 
>>
>> https://github.com/orgs/jenkinsci/teams/code-reviewers
>>
>> is open to *anyone* willing to review Jenkins code in general (core or 
>> plugins). Either you want to grow your skills, or help in general, or both, 
>> this is one good place.
>>
>> Note that being part of that team does *not* require you to review 
>> anything where you get asked to.
>>
>> Le 6 janv. 2016 9:42 PM, "Baptiste Mathus"  a écrit :
>>
>>> Hi everyone,
>>>
>>> If you've already tried to get feedback on a PR you were working on, or 
>>> are interested in helping & learning things by reviewing other's code, read 
>>> on.
>>>
>>> Daniel just helped set up a Jenkinsci GitHub organization new sub-team 
>>> called '*code-reviewers*' to define a group of people willing to try 
>>> and review code at the request of others.
>>>
>>>- If you want to be part of it, click on the right button on that 
>>>page: 
>>>   https://github.com/orgs/jenkinsci/teams/code-reviewers
>>>
>>>- If you want to notify that team (and get reviewed) in a comment, 
>>>use the *@jenkinsci/code-reviewers* form (should autocomplete).
>>>
>>> Here it is. This is something we wanted to try and still very early in 
>>> the process, don't hesitate to tell us what you think of it here or on IRC.
>>>
>>> Hope you find it useful!
>>>
>>> Cheers
>>>
>>> -- Baptiste
>>>
>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/f1a601af-79a9-434b-b3f9-493941e8905f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Not able to release new version of plugin

[Daniel Beck]

> On 05.01.2017, at 15:15, Irfan Sayed  wrote:
> 
> still the same error

Unsurprising given that this still referenced the host name that has been shut 
down.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/6EF8E60C-351D-43F5-B873-B201E5F32FC9%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Not able to release new version of plugin

[Irfan Sayed]

Thanks Daniel.
i added following in plugin POM:



  java.net-m2-repository
  http://maven.jenkins-ci.org/content/repositories/releases/

  

still the same error. i am not getting from where it is picking up that url
and port number.
in my settings.xml as well this URL is not there

Regards,


On Thu, Jan 5, 2017 at 6:03 AM, Daniel Beck  wrote:

>
> > On 05.01.2017, at 15:02, Irfan Sayed  wrote:
> >
> > In my plugins POM, i have already this:
>
> What about distributionManagement?
>
> --
> 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.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/CE94F05B-D736-4F6B-8BC2-CAAD18A83C4B%40beckweb.net.
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CACGLCJZb_MPAKnr7OuPz10VUBCqP1Vs7Sj0kGKSTzEd0hrdWYQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Not able to release new version of plugin

[Daniel Beck]

> On 05.01.2017, at 15:02, Irfan Sayed  wrote:
> 
> In my plugins POM, i have already this:

What about distributionManagement?

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CE94F05B-D736-4F6B-8BC2-CAAD18A83C4B%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Not able to release new version of plugin

[Irfan Sayed]

Thanks Daniel.
In my plugins POM, i have already this:

 

  repo.jenkins-ci.org
  http://repo.jenkins-ci.org/public/

  
  

  repo.jenkins-ci.org
  http://repo.jenkins-ci.org/public/

  

is this not correct ?
Regards,


On Thu, Jan 5, 2017 at 5:57 AM, Daniel Beck  wrote:

>
> > On 05.01.2017, at 14:49, Irfan Sayed  wrote:
> >
> > it seems that URL : http://maven.jenkins-ci.org:
> 8081/content/repositories/releases is not working.
> > Can someone please suggest ?
>
> Second item at https://wiki.jenkins-ci.org/display/JENKINS/Hosting+
> Plugins#HostingPlugins-Workingaroundcommonissues
>
> --
> 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.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/BAD647E8-726F-43FA-BCE0-2153E08E0E82%40beckweb.net.
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CACGLCJas2wgPhsEmz5yBzxYG_SyF0V_Q1yHcW_xKeMn9tGS-EQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Not able to release new version of plugin

[Daniel Beck]

> On 05.01.2017, at 14:49, Irfan Sayed  wrote:
> 
> it seems that URL : 
> http://maven.jenkins-ci.org:8081/content/repositories/releases is not working.
> Can someone please suggest ? 

Second item at 
https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Workingaroundcommonissues

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/BAD647E8-726F-43FA-BCE0-2153E08E0E82%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.