Skip to content

Conversation

@mkramb
Copy link

@mkramb mkramb commented Oct 4, 2018

No description provided.

@ryanjwilke
Copy link
Contributor

Thanks for helping get this started :)

Rakefile Outdated

desc 'Publish project to npm as scoped package @codeship/shipyard'
task :console do
sh 'npm publish --access public'
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are the files builded by then (e.g. sass 2 css)?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

They can be. The sass files will always be ready to go, but the css would need to be compiled first, yes.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To be clear though, there's no requirement that the CSS is packaged as the best way to consume all of this will be through the sass files anyways.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's start with sass. For some playground or prototyping it would be useful to have compiled versions, but we don't have a use-case for that ATM.

Rakefile Outdated

desc 'Publish project to npm as scoped package @codeship/shipyard'
task :console do
sh 'npm publish --access public'
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Imo that needs to be the last part of the rakefile.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated.

@ryanjwilke ryanjwilke mentioned this pull request Oct 4, 2018
Rakefile Outdated

desc 'Publish project to npm as a scoped package @codeship/shipyard'
task :console do
sh 'npm publish --access public'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Two questions:

  1. Does this need to authenticate with anything?
  2. Do we need to add this command to the CI deploy stage?

set -e # halt script on error

echo -e "\n\n************** NPM publish for @codeship/shipyard **************"
npm publish --access public No newline at end of file
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Apologies, I misunderstood the build system,
this should be called as a step on master branch - same as other scripts.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@codebryo @ryanjwilke
Do we need to authenticate against NPM or is that configured automatically for the build? How are you doing that for other NPM codeship packages - which have scoped package @codeship

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would assume that would be injected as environment variables from the pipeline configuration.

service: shipyard
name: GitHub Pages
command: ./ci/github
-
Copy link
Author

@mkramb mkramb Oct 4, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will be executed only on master branch.

@joesiewert joesiewert marked this pull request as draft November 2, 2020 19:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

4 participants