Hi All,
Now I am able to see the latest plugin in sites.
On Thursday, April 2, 2020 at 2:02:52 PM UTC+5:30, selva vignesh wrote:
>
> Hi,
> I have published my plugin and added Wiki in Readme.md in github.
> But still i am unable to find wiki in
> https://plugins.jenkins.io/zohosprints/
> can
Possibly that could have an impact
I’m hoping to look at this soon
On Tue, 7 Apr 2020 at 18:30, Mark Waite wrote:
> Interesting. I see the same outdated page that you show in your
> screenshot.
>
> The ci.jenkins.io build queue is quite long right now. The acceptance
> test harness is
Interesting. I see the same outdated page that you show in your
screenshot.
The ci.jenkins.io build queue is quite long right now. The acceptance test
harness is processing pull requests and will likely be doing that for a few
more hours. That might be blocking some processing of updates of
Right now it is up to date. But it is not the case all the time.
I can't tell when exactly it was out of date, but I saw it multiple times
out of date and back up to date a couple hours later.
As if it was load balanced and one of the backends is out of date, except
that refreshing or emptying
I'm seeing the current releases for docker-java-api and docker-plugin when
I view them through https://plugins.jenkins.io/ .
Are you still seeing them shown as out of date?
Have you forced a refresh of your browser?
On Tue, Apr 7, 2020 at 6:16 AM Eric Citaire wrote:
> I'm experiencing the
I'm experiencing the same behavior on other plugins released
recently (docker-plugin and docker-java-api). The plugins site keeps
rolling back to the old version.
I think there is a real problem with the plugins site.
Le mardi 7 avril 2020 11:09:12 UTC+2, selva vignesh a écrit :
>
> Galvin,
Galvin, for an hour back, I was able to see the documentation in plugin
site. But now, seems reverted to 1.0 release.
Do i need to do anything from my side. please assist.
On Tue, Apr 7, 2020 at 12:23 PM selva vignesh
wrote:
> Gavin, I'll proper release tag for upcoming releases
>
> On Tue, Apr
Gavin, I'll proper release tag for upcoming releases
On Tue, Apr 7, 2020 at 11:15 AM 'Gavin Mogan' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:
> I see 1.1 at http://updates.jenkins-ci.org/download/plugins/zohosprints/
>
> i also see 1.0.2, which you don't seem to have a
I see 1.1 at http://updates.jenkins-ci.org/download/plugins/zohosprints/
i also see 1.0.2, which you don't seem to have a tag/release for
I'm very confused by the state of your repo.
On Mon, Apr 6, 2020 at 8:41 PM selva vignesh
wrote:
> yes Slide. I am referring releasing plugin as a build.
yes Slide. I am referring releasing plugin as a build. Sorry for the
confusion.
Sure Gavin. I will release one more build without hyphen.
On Tue, Apr 7, 2020 at 9:08 AM 'Gavin Mogan' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:
> 11 days ago is a suspicious number, none of
11 days ago is a suspicious number, none of them line up with
https://github.com/jenkinsci/zohosprints-plugin/releases
I'm honestly not sure what will happen when you add values after the
version number (ex 1.0.3-docrelease), i know beta and alpha goto
experimental. Can you do a proper "1.0.3" or
When you say updated a build,do you mean you create a new release of the
plugin? Can you point to your pom.xml?
On Mon, Apr 6, 2020 at 8:34 PM selva vignesh
wrote:
> Hi,
> After adding value to GitHub repo nothing changed. I have updated a
> build yesterday but still in plugin page showing
Hi,
After adding value to GitHub repo nothing changed. I have updated a
build yesterday but still in plugin page showing that Last release was 11
days ago. can anyone please assist
On Thu, Apr 2, 2020 at 3:23 PM Richard Bywater wrote:
> Hi
>
> The value in your pom.xml needs to point at your
Hi
The value in your pom.xml needs to point at your Github repository
(i.e. https://github.com/jenkinsci/zohosprints-plugin) for the plugin site
to use the README from your Github repo.
Richard.
On Thu, 2 Apr 2020 at 21:33, selva vignesh
wrote:
> Hi,
> I have published my plugin and added
Hi,
I have published my plugin and added Wiki in Readme.md in github.
But still i am unable to find wiki in
https://plugins.jenkins.io/zohosprints/
can anyone please assist.
Thanks in advance
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers"
nsci-dev@googlegroups.com>
Sent: Monday, March 14, 2016 9:08 AM
Subject: Re: Jenkins Plugin Wiki say "No Information For this Plugin"
Here you go "mvn release:prepare release:perform"
my github username/passwd is same as jenkins and is set in settings.xml and
ssh key
opers <jenkinsci-dev@googlegroups.com>
> *To:* "jenkinsci-dev@googlegroups.com" <jenkinsci-dev@googlegroups.com>
> *Sent:* Monday, March 14, 2016 9:08 AM
>
> *Subject:* Re: Jenkins Plugin Wiki say "No Information For this Plugin"
>
> Here you go "mvn rel
enkinsci-dev@googlegroups.com>
Sent: Monday, March 14, 2016 9:08 AM
Subject: Re: Jenkins Plugin Wiki say "No Information For this Plugin"
Here you go "mvn release:prepare release:perform"
my github username/passwd is same as jenkins and is set in settings.xml and
ssh
on the wiki. Any idea
how much ?
From: 'srikant' via Jenkins Developers <jenkinsci-dev@googlegroups.com>
To: "jenkinsci-dev@googlegroups.com" <jenkinsci-dev@googlegroups.com>
Sent: Monday, March 14, 2016 9:08 AM
Subject: Re: Jenkins Plugin Wiki say "No Informatio
Cc: sri...@yahoo.com
Sent: Monday, March 14, 2016 5:17 AM
Subject: Re: Jenkins Plugin Wiki say "No Information For this Plugin"
Hmm... The plugin has not been uploaded to the Maven repo
Maven output:
[INFO] [INFO] --- maven-deploy-plugin:2.6:deploy (default-deploy) @ ca-apm ---
Hmm... The plugin has not been uploaded to the Maven repo
Maven output:
[INFO] [INFO] --- maven-deploy-plugin:2.6:deploy (default-deploy) @ ca-apm ---
[INFO] [INFO] Skipping artifact deployment
Could you provide mvn options you use to run the command?
понедельник, 14 марта 2016 г., 5:04:58
Looks like your release wasn't fully performed, no artefacts where
uploaded, not even snapshots.
Maybe because of the Javadoc warning? or did you run release:perform ?
/B
On Mon, Mar 14, 2016 at 5:04 AM, srikns via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:
>
> Hi
> I
Hi I published a plugin on github
jenkinsci/ca-apm-plugin and created a wiki
https://wiki.jenkins-ci.org/display/JENKINS/CA+APM+Plugin, am having trouble
pulling the plugin information on wiki and if you open the wiki you will see it
says "No
On Wed, Sep 16, 2015 at 12:48 AM, Daniel Beck wrote:
> You need Maven to do anything anyway, and `mvn -U
> org.jenkins-ci.tools:maven-hpi-plugin:create` is trivial to run. Yet we have
> some random service that does basically the same thing
Agreed, I think the effort would be
+1 - I think the resources to create & keep stuff running is already
stretched so having something that doesn't really add any value just seems
to be throwing people's time away?
Richard.
On Wed, 16 Sep 2015 at 16:48 Daniel Beck wrote:
> I never understood this. You need
I never understood this. You need Maven to do anything anyway, and `mvn -U
org.jenkins-ci.tools:maven-hpi-plugin:create` is trivial to run. Yet we have
some random service that does basically the same thing needs to be kept running
-- something we're clearly not good at.
What am I missing?
On
Yeah, we lost this service. I need to find a new home for it, but I got a
bit of push back from other admins about running a random service like this.
Maybe if we wrap this into a container and make sure it gets auto-restarted
when it dies, perhaps that would help reduce the operational
This was me — I renamed that page to fit the usual convention, so please
use that URL in future:
https://wiki.jenkins-ci.org/display/JENKINS/Violation+Comments+to+Stash+Plugin
However, there's an annoying bug in that deleted or renamed pages remain
in the wiki static cache, for which I will
28 matches
Mail list logo