Added the snapcraft PR job.

[elopio]

No description provided.

[elopio]

@fgimenez I'm not sure if this will be the way to install deps in the slaves.

[fgimenez]

IMO it would be better to do that in the Dockerfile, we don't need to repeat these steps on each job execution, even if only the first one would do the actual installation. When the slaves will be ephemeral it will make even more sense, they will need to spawn with all the required dependencies installed, if not, because they will die when the job finishes, the installation will happen on each execution.

[elopio]

@fgimenez it seems that this command is not installed in the current jenkins. Reprovisioning it would get the newer snappy-jenkins-job?

[fgimenez]

mm you mean snappy-cloud-image and snappy-tests-job, right? :) Reprovisioning will get the latest available versions of both executables, now that we are using slaves they will get installed there instead of the master.

However I think that you don't need to create the image from the job, there are specific jobs that are polling system-image (mental note, we should modify this to target the store somehow), generate the image and trigger a downstream job to test it. Is that enough or am I missing something?

[fgimenez]

Ok, now I understand, snappy-cloud-client comes with the latest snappy-tests-job, if you try a fresh deploy with the current tip of master it should be available there

[fgimenez]

👍 only needing to move the package installation to the slave's Dockerfile

[elopio]

Thanks for the review @fgimenez. I moved the deps to the Dockerfile. Please take another look.

[fgimenez]

ok thanks!