Updated the Personal Access Token,

I note the chmod is failing as Jenkins does not have permission to modify
exe uploaded by prior run. Deleting the file allowed to verify that the
access token works (and installer was uploaded).


Trying to change the file group to jenkins so this should not happen in the
future:

-rw-rw-r-- 1 azurebuild jenkins 110M Nov 18 16:19
GeoServer-2.22.0-winsetup.exe

But this did not resolve the issue; and chmod failed on the next attempt.

chmod: changing permissions of
'/var/lib/jenkins/jobs/geoserver-release/builds/92/archive/distribution/2.22.0/GeoServer-2.22.0-winsetup.exe':
Operation not permitted

I expect that as a normal user jenkins cannot change ownership of a file (w
access for the group is not sufficient for chown?)
--
Jody Garnett


On Nov 18, 2022 at 4:39:37 AM, Juan Luis Rodriguez Ponce <
juanlui...@geocat.net> wrote:

> ---- On Fri, 18 Nov 2022 12:47:06 +0100 *Andrea Aime
> <andrea.a...@geosolutionsgroup.com <andrea.a...@geosolutionsgroup.com>>*
> wrote ---
>
> Hi Juan,
> thanks for doing that!
>
> Looks like the release job was not used, it's still red, so I assume you
> run the creation on your own.
> What needs to be done, in order to get that job fixed and running
> automatically when we need to?
>
>
> I guess I or Jody need to generate a Personal Access Token in Azure Dev,
> update the current secret (AZURE_WINDOWS_CREDENTIALS) used by the job in
> Jenkins. The project changed to a new organization and the old PAT stopped
> working. Probably Jody has enough permissions to update the secret.
>
> Best regards,
> Juan Luis.
>
>
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Reply via email to