Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Pharo build failures caused by deployment step #160

Closed
fniephaus opened this issue Oct 25, 2017 · 6 comments
Closed

Pharo build failures caused by deployment step #160

fniephaus opened this issue Oct 25, 2017 · 6 comments
Assignees
@estebanlm
Labels
bug CI Pharo
Projects
Next Release
Milestone
Release 2 (next)

Comments

@fniephaus
Copy link
Member

Example from this build:

Uploading ./pharo-linux-x86_64itimer-201710221351-1a23fe1.zip to pharo.files.org//appli/files.pharo.org/vm/pharo-spur64/linux
Warning: Permanently added the RSA host key for IP address '193.51.193.142' to the list of known hosts.
Uploading ./pharo-linux-x86_64itimer-201710221351-1a23fe1.zip to pharo.files.org//appli/files.pharo.org/vm/pharo-spur64/linux/latest.zip
scp: /appli/files.pharo.org/vm/pharo-spur64/linux/latest.zip: Permission denied
Script failed with status 1
@fniephaus fniephaus added this to the Next Release milestone Nov 15, 2017
@fniephaus fniephaus added this to To Do in Next Release Nov 15, 2017
@fniephaus fniephaus added the CI label Nov 15, 2017
Next Release automation moved this from To Do to Done Dec 17, 2017
fniephaus added a commit that referenced this issue Dec 17, 2017
@fniephaus
Further simplify .travis.yml.
b183fd4 
Also, add IP address to SSH known hosts instead of domain (#160).
@fniephaus
Copy link
Member Author

The issue persists. Reverting my latest changes and disabling Pharo deploy to unblock the build pipeline. Please fix @estebanlm.

@fniephaus fniephaus reopened this Dec 17, 2017
@estebanlm
Copy link
Contributor

estebanlm commented Dec 17, 2017 •
edited

I know Christophe was working on it, but I do not know if he finished (And I didn't have the time to work on it myself). I guess next week we will have a solution.

fniephaus added a commit that referenced this issue Dec 17, 2017
@fniephaus
Revert attempt to address #160.
ebe0000 
Disable pharo deployment temporarily.
@fniephaus
Copy link
Member Author

No problem. Change this to enable Pharo deployment again when Christophe or you have time to fix it.

@estebanlm
Copy link
Contributor

this is done, isn't @fniephaus ?

@estebanlm
Copy link
Contributor

I mean, now we have the packaging problem (which I will fix today), but this is done, AFAIK

@fniephaus
Copy link
Member Author

Yes, this is fixed....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@estebanlm estebanlm

Labels
bug CI Pharo
Projects
Next Release
  
Done
Milestone
Release 2 (next)
Development

No branches or pull requests
2 participants
@estebanlm @fniephaus