What about the Jenkins job configuration changes? 

I see there were changes in the failed builds. I don’t have a Jenkins account 
right now, so I can not access the change diff log.

Links below are the change diff logs, in the order of first failed build to 
most recent.

https://builds.apache.org/job/cordova-nightly/jobConfigHistory/showDiffFiles?timestamp1=2018-07-19_04-45-08&timestamp2=2018-07-19_04-56-48
 
<https://builds.apache.org/job/cordova-nightly/jobConfigHistory/showDiffFiles?timestamp1=2018-07-19_04-45-08&timestamp2=2018-07-19_04-56-48>

https://builds.apache.org/job/cordova-nightly/jobConfigHistory/showDiffFiles?timestamp1=2018-07-19_04-56-48&timestamp2=2018-07-19_04-58-04
 
<https://builds.apache.org/job/cordova-nightly/jobConfigHistory/showDiffFiles?timestamp1=2018-07-19_04-56-48&timestamp2=2018-07-19_04-58-04>

https://builds.apache.org/job/cordova-nightly/jobConfigHistory/showDiffFiles?timestamp1=2018-07-19_04-58-04&timestamp2=2018-07-19_04-59-19
 
<https://builds.apache.org/job/cordova-nightly/jobConfigHistory/showDiffFiles?timestamp1=2018-07-19_04-58-04&timestamp2=2018-07-19_04-59-19>

https://builds.apache.org/job/cordova-nightly/jobConfigHistory/showDiffFiles?timestamp1=2018-07-19_04-59-19&timestamp2=2018-07-19_05-00-03
 
<https://builds.apache.org/job/cordova-nightly/jobConfigHistory/showDiffFiles?timestamp1=2018-07-19_04-59-19&timestamp2=2018-07-19_05-00-03>
 

> On Jul 21, 2018, at 14:25, Darryl Pogue <dar...@dpogue.ca> wrote:
> 
> cordova-create and cordova-fetch both appear to have the correct
> (nightly) version number in package.json.
> 
> As far as I know, nothing has changed recently that explains why this
> is suddenly happening :(
> 
> On Fri, Jul 20, 2018 at 9:44 PM Bryan Ellis <ellis.br...@gmail.com 
> <mailto:ellis.br...@gmail.com>> wrote:
>> 
>> Ah, I didn’t see the npm ERR! line in your previous message. I see I missed 
>> it.
>> 
>> I tried pulling out and testing only the snippet of code that updates the 
>> package.json and runs the pendingChangesExist methind. Locally, against the 
>> cli repo, it updates the package.json OK and the message "package.json file 
>> was already up-to-date” was not displayed.
>> 
>> Does cordova-fetch and cordova-create have any issue? I noticed those two 
>> also display the message “package.json file was already up-to-date."
>> 
>>> On Jul 21, 2018, at 12:49, Darryl Pogue <dvpdin...@gmail.com> wrote:
>>> 
>>> Yeah, it *should* be trying to publish 8.0.1-nightly.2008.7.21.77b7324f
>>> 
>>> But the package.json never successfully got updated, as seen in the
>>> workspace here:
>>> https://builds.apache.org/job/cordova-nightly/ws/cordova-cli/package.json/*view*/
>>>  
>>> <https://builds.apache.org/job/cordova-nightly/ws/cordova-cli/package.json/*view*/>
>>>  
>>> <https://builds.apache.org/job/cordova-nightly/ws/cordova-cli/package.json/*view*/
>>>  
>>> <https://builds.apache.org/job/cordova-nightly/ws/cordova-cli/package.json/*view*/>>
>>> (Compare to 
>>> https://builds.apache.org/job/cordova-nightly/ws/cordova-common/package.json/*view*/
>>>  
>>> <https://builds.apache.org/job/cordova-nightly/ws/cordova-common/package.json/*view*/>
>>>  
>>> <https://builds.apache.org/job/cordova-nightly/ws/cordova-common/package.json/*view*/
>>>  
>>> <https://builds.apache.org/job/cordova-nightly/ws/cordova-common/package.json/*view*/>>
>>> which did get updated)
>>> 
>>> The problem is I don't know why coho isn't properly updating the
>>> package.json for this one repo.
>>> 
>>> On Fri, Jul 20, 2018 at 8:42 PM Bryan Ellis <ellis.br...@gmail.com 
>>> <mailto:ellis.br...@gmail.com> <mailto:ellis.br...@gmail.com 
>>> <mailto:ellis.br...@gmail.com>>> wrote:
>>>> 
>>>> From what I am read in the artifact, it is actually trying to publish 
>>>> 8.0.1-dev. This version already exists and had been published 7 months ago.
>>>> 
>>>> What I suspect and what we think it is trying to publish is 
>>>> 8.0.1-nightly.2018.7.21.77b7324f but seem that is not what is being sent.
>>>> 41 verbose stack Error: You cannot publish over the previously published 
>>>> versions: 8.0.1-dev. : cordova
>>>> https://builds.apache.org/job/cordova-nightly/795/artifact/cordova-cli/npm-debug.log
>>>>  
>>>> <https://builds.apache.org/job/cordova-nightly/795/artifact/cordova-cli/npm-debug.log>
>>>>  
>>>> <https://builds.apache.org/job/cordova-nightly/795/artifact/cordova-cli/npm-debug.log
>>>>  
>>>> <https://builds.apache.org/job/cordova-nightly/795/artifact/cordova-cli/npm-debug.log>>
>>>>  
>>>> <https://builds.apache.org/job/cordova-nightly/795/artifact/cordova-cli/npm-debug.log
>>>>  
>>>> <https://builds.apache.org/job/cordova-nightly/795/artifact/cordova-cli/npm-debug.log><https://builds.apache.org/job/cordova-nightly/795/artifact/cordova-cli/npm-debug.log
>>>>  
>>>> <https://builds.apache.org/job/cordova-nightly/795/artifact/cordova-cli/npm-debug.log>>>
>>>> 
>>>> I hope that might help help...
>>>> 
>>>> 
>>>>> On Jul 21, 2018, at 12:27, Darryl Pogue <dvpdin...@gmail.com> wrote:
>>>>> 
>>>>> Okay, the latest nightly failures are some sort of bug in coho when it
>>>>> tries to update the version number in the package.json:
>>>>> 
>>>>> cordova-cli/ =================== Updating cli version to
>>>>> 8.0.1-nightly.2018.7.21.77b7324f
>>>>> cordova-cli/ =================== package.json file was already up-to-date.
>>>>> ...
>>>>> npm ERR! You cannot publish over the previously published versions:
>>>>> 8.0.1-dev. : cordova
>>>>> 
>>>>> So it claims to be updating the version number, says that it didn't
>>>>> make any changes, and then fails to publish because the version number
>>>>> matches something already published. It looks like all the other repos
>>>>> are getting their package.json version numbers properly incremented,
>>>>> but none are getting published because it hits this error first.
>>>>> 
>>>>> I quickly skimmed over the coho code yesterday, and it's a pretty
>>>>> basic case of loading package.json as JSON, assigning the version, and
>>>>> writing out a stringified copy, so I have no idea what's going wrong
>>>>> :(
>>>>> 
>>>>> 
>>>>> On Fri, Jul 20, 2018 at 7:51 PM Apache Jenkins Server
>>>>> <jenk...@builds.apache.org> wrote:
>>>>>> 
>>>>>> Nightly build #795 for cordova has failed.
>>>>>> 
>>>>>> Please check failure details on build details page at 
>>>>>> https://builds.apache.org/job/cordova-nightly/795/
>>>>>> You can also take a look at build console: 
>>>>>> https://builds.apache.org/job/cordova-nightly/795/consoleFull
>>>>>> 
>>>>>> -
>>>>>> Jenkins for Apache Cordova
>>>>>> 
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
>>>>>> For additional commands, e-mail: dev-h...@cordova.apache.org
>>>>> 
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
>>>>> For additional commands, e-mail: dev-h...@cordova.apache.org
>>>>> 
>>>> 
>>> 
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org 
>>> <mailto:dev-unsubscr...@cordova.apache.org> 
>>> <mailto:dev-unsubscr...@cordova.apache.org 
>>> <mailto:dev-unsubscr...@cordova.apache.org>>
>>> For additional commands, e-mail: dev-h...@cordova.apache.org 
>>> <mailto:dev-h...@cordova.apache.org> <mailto:dev-h...@cordova.apache.org 
>>> <mailto:dev-h...@cordova.apache.org>>
>>> 
>> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org 
> <mailto:dev-unsubscr...@cordova.apache.org>
> For additional commands, e-mail: dev-h...@cordova.apache.org 
> <mailto:dev-h...@cordova.apache.org>
> 

Reply via email to