I let pono know on Friday (via #lucene IRC) that the -Artifacts jobs were still not being triggered, and he said he would research the Authorization plugin.
Todo I pinged pono on #lucene IRC again, and he said the next thing to try was to configure the Authorization plugin as “Run as Anonymous”. I’ve done that, and have manually scheduled the two -Nightly jobs to run next. If this doesn’t get cleared up soon, I’ll just switch the -Artifacts jobs to run periodically (@daily) instead of downstream from the -Nightly jobs. (I don’t think this connection is really useful anyway.) -- Steve www.lucidworks.com > On May 7, 2017, at 4:15 PM, Mikhail Khludnev <[email protected]> wrote: > > Hello, Steve. > I notice the same authorization warning at > https://builds.apache.org/job/Lucene-Solr-NightlyTests-6.x/343/console > Do you know if there is a chance to get a nightly build? > > On Tue, May 2, 2017 at 6:43 PM, Steve Rowe <[email protected]> wrote: > Mikhail alerted me to the fact that the Lucene-Artifacts-6.x job hasn’t run > recently on ASF Jenkins. This job is a “downstream project” of > Lucene-Solr-NightlyTests-6.x, i.e. once the latter has finished building, the > former is triggered. (Solr-Artifacts-6.x is a downstream project of > Lucene-Artifacts-6.x, so as a result of this problem, it hasn’t run recently > either.) > > I see the following in the log from the most recent > Lucene-Solr-NightlyTests-6.x build > <https://builds.apache.org/job/Lucene-Solr-NightlyTests-6.x/337/console>: > > ----- > Warning: this build has no associated authentication, so build permissions > may be lacking, and downstream projects which cannot even be seen by an > anonymous user will be silently skipped > You have no permission to build Lucene-Artifacts-6.x > ----- > > Lucene-Solr-NightlyTests-master/Lucene-Artifacts-master is exhibiting the > same behavior - the oldest retained log from April 28th > <https://builds.apache.org/job/Lucene-Solr-NightlyTests-master/1288/console> > has the same warning/permission text ^^. > > I mentioned the problem on Infra’s hipchat channel, and pono (Daniel > Takamori), chatting with me on #lucene IRC, suggested the problem started > with the Jenkins upgrade over the weekend, but the April 28th build predates > that. pono also noted that the Jenkins upgrade brought a new capability: the > Jenkins Build Authorization plugin. He had me configure the two jobs in > question to first enable “Configure Build Authorization” and then select “Run > as user who triggered build”. This is an experiment: we’ll see how it goes. > (I’m wondering if this will cause a problem with manually kicked off jobs.) > > I’ll keep an eye on it but if anybody else notices problems, please let us > know. > > -- > Steve > www.lucidworks.com > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > > > -- > Sincerely yours > Mikhail Khludnev --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
