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.

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

change the release extension from .gz to .tar.gz #2009

Merged

Conversation

girishramnani
Copy link
Contributor

@girishramnani girishramnani commented Aug 12, 2019

What is the purpose of this change? What does it change?

see $SUBJECT.

Was the change discussed in an issue?

fixes #1994

How to test changes?

make prepare-release should create

@kadel
Copy link
Member

kadel commented Aug 14, 2019

/approve

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. Required by Prow. label Aug 14, 2019
@kadel
Copy link
Member

kadel commented Aug 19, 2019

/assign @amitkrout @mohammedzee1000

Copy link
Contributor

@amitkrout amitkrout left a comment

Choose a reason for hiding this comment

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

$ make prepare-release
gox -osarch="darwin/amd64 linux/amd64 windows/amd64" -output="dist/bin/{{.OS}}-{{.Arch}}/odo" -ldflags="-w -X github.com/openshift/odo/pkg/odo/cli/version.GITCOMMIT=e017230d" ./cmd/odo/
Number of parallel builds: 7

-->     linux/amd64: github.com/openshift/odo/cmd/odo
-->    darwin/amd64: github.com/openshift/odo/cmd/odo
-->   windows/amd64: github.com/openshift/odo/cmd/odo
./scripts/prepare-release.sh
gzipping binary ./dist/bin/darwin-amd64/odo as ./dist/release/odo-darwin-amd64
a odo
copying binary ./dist/bin/darwin-amd64/odo to release directory
gzipping binary ./dist/bin/linux-amd64/odo as ./dist/release/odo-linux-amd64
a odo
copying binary ./dist/bin/linux-amd64/odo to release directory
gzipping binary ./dist/bin/windows-amd64/odo.exe as ./dist/release/odo-windows-amd64.exe
a odo.exe
copying binary ./dist/bin/windows-amd64/odo.exe to release directory
generating SHA256_SUM for release packages
find: -printf: unknown primary or operator
The SHA256 SUM for the release packages are:
Amits-MacBook-Pro:odo amit$

@girishramnani I have tested it on my macOS and found here are no SHA256 SUM for the release packages. Can you please have a look

And we can merge it even now, right ? if yes, then remove the phrase Open [Merge immediately before release]: from the title of the pr.

@girishramnani
Copy link
Contributor Author

@amitkrout no we cannot merge it right now because the documentation would say odo.tar.gz which will only happen until next release. So from the time we merge this to the next release, the docs would be inconsistent

@kadel
Copy link
Member

kadel commented Aug 21, 2019

@amitkrout no we cannot merge it right now because the documentation would say odo.tar.gz which will only happen until next release. So from the time we merge this to the next release, the docs would be inconsistent

can we split this into two PRs? On that updates scripts, we can merge it now. And the other that will update just docs, that we can merge after the release?

@amitkrout
Copy link
Contributor

amitkrout commented Aug 22, 2019

@amitkrout no we cannot merge it right now because the documentation would say odo.tar.gz which will only happen until next release. So from the time we merge this to the next release, the docs would be inconsistent

can we split this into two PRs? On that updates scripts, we can merge it now. And the other that will update just docs, that we can merge after the release?

It should not effect the released version doc of for example beta4 because the patching is done against master branch until the next release.

Can you point out which doc and the references reflect the changes

@girishramnani I have tested it on my macOS and found here are no SHA256 SUM for the release packages. Can you please have a look

Please address this too

README.adoc Outdated
@@ -69,7 +69,7 @@ For more installation options please refer the link:docs/installation.adoc[insta
In order to correctly use `odo` you must download it and add it
to your `PATH` environment variable:

. Download the `odo-windows-amd64.exe.gz` file from the
. Download the `odo-windows-amd64.exe.tar.gz` file from the
Copy link
Contributor Author

Choose a reason for hiding this comment

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

@amitkrout this change

Copy link
Contributor

@amitkrout amitkrout Aug 22, 2019

Choose a reason for hiding this comment

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

Ok, then it will comes to effect only when the very next release happen or somebody wants to run release locally on master. Correct me if i am wrong.

Doc changes on master won't effect doc of any old release, right ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

docs merged in would directly show up on github, and I think isn't that the place where people go to for docs? I dont think we release docs on a separate website. so if I merge this now people will see this as the current docs.

@@ -63,7 +63,7 @@ $ brew install kadel/odo/odo
==== Tarball installation

----
# sh -c 'curl -L https://github.com/openshift/odo/releases/latest/download/odo-darwin-amd64.gz | gzip -d > /usr/local/bin/odo; chmod +x /usr/local/bin/odo'
# sh -c 'curl -L https://github.com/openshift/odo/releases/latest/download/odo-darwin-amd64.tar.gz | tar -xvzf odo-darwin-amd64.tar.gz -C /usr/local/bin; chmod +x /usr/local/bin/odo'
Copy link
Contributor Author

Choose a reason for hiding this comment

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

@amitkrout this change

Copy link
Contributor

Choose a reason for hiding this comment

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

@@ -109,7 +109,7 @@ $ echo "deb https://dl.bintray.com/odo/odo-deb-releases stretch main" | sudo tee
==== Tarball installation

----
# sh -c 'curl -L https://github.com/openshift/odo/releases/latest/download/odo-linux-amd64.gz | gzip -d > /usr/local/bin/odo; chmod +x /usr/local/bin/odo'
# sh -c 'curl -L https://github.com/openshift/odo/releases/latest/download/odo-linux-amd64.tar.gz | tar -xvzf odo-linux-amd64.tar.gz -C /usr/local/bin; chmod +x /usr/local/bin/odo'
Copy link
Contributor Author

Choose a reason for hiding this comment

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

@amitkrout this change

Copy link
Contributor

Choose a reason for hiding this comment

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

@@ -179,7 +179,7 @@ $ dnf install odo
==== Tarball installation

----
# sh -c 'curl -L https://github.com/openshift/odo/releases/latest/download/odo-linux-amd64.gz | gzip -d > /usr/local/bin/odo; chmod +x /usr/local/bin/odo'
# sh -c 'curl -L https://github.com/openshift/odo/releases/latest/download/odo-linux-amd64.tar.gz | tar -xvzf odo-linux-amd64.tar.gz -C /usr/local/bin; chmod +x /usr/local/bin/odo'
Copy link
Contributor Author

Choose a reason for hiding this comment

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

@amitkrout this change

Copy link
Contributor

Choose a reason for hiding this comment

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

@girishramnani
Copy link
Contributor Author

@amitkrout no we cannot merge it right now because the documentation would say odo.tar.gz which will only happen until next release. So from the time we merge this to the next release, the docs would be inconsistent

can we split this into two PRs? On that updates scripts, we can merge it now. And the other that will update just docs, that we can merge after the release?

It should not effect the released version doc of for example beta4 because the patching is done against master branch until the next release.

Can you point out which doc and the references reflect the changes

@girishramnani I have tested it on my macOS and found here are no SHA256 SUM for the release packages. Can you please have a look

Please address this too

@amitkrout I don't have a macOS machine to reproduce this. Can you help me get more information on this?

@girishramnani
Copy link
Contributor Author

@amitkrout no we cannot merge it right now because the documentation would say odo.tar.gz which will only happen until next release. So from the time we merge this to the next release, the docs would be inconsistent

can we split this into two PRs? On that updates scripts, we can merge it now. And the other that will update just docs, that we can merge after the release?

Makes sense, doing that now @kadel

@amitkrout
Copy link
Contributor

@amitkrout no we cannot merge it right now because the documentation would say odo.tar.gz which will only happen until next release. So from the time we merge this to the next release, the docs would be inconsistent

can we split this into two PRs? On that updates scripts, we can merge it now. And the other that will update just docs, that we can merge after the release?

It should not effect the released version doc of for example beta4 because the patching is done against master branch until the next release.
Can you point out which doc and the references reflect the changes

@girishramnani I have tested it on my macOS and found here are no SHA256 SUM for the release packages. Can you please have a look

Please address this too

@amitkrout I don't have a macOS machine to reproduce this. Can you help me get more information on this?

On fedora no such issue occurred. The error is coming from line https://github.com/openshift/odo/pull/2009/files#diff-2ae5224a8073d5cd24ce33fe39d5bfa8R45 on mac host

generating SHA256_SUM for release packages
find: -printf: unknown primary or operator

@girishramnani
Copy link
Contributor Author

@amitkrout no we cannot merge it right now because the documentation would say odo.tar.gz which will only happen until next release. So from the time we merge this to the next release, the docs would be inconsistent

can we split this into two PRs? On that updates scripts, we can merge it now. And the other that will update just docs, that we can merge after the release?

It should not effect the released version doc of for example beta4 because the patching is done against master branch until the next release.
Can you point out which doc and the references reflect the changes

@girishramnani I have tested it on my macOS and found here are no SHA256 SUM for the release packages. Can you please have a look

Please address this too

@amitkrout I don't have a macOS machine to reproduce this. Can you help me get more information on this?

On fedora no such issue occurred. The error is coming from line https://github.com/openshift/odo/pull/2009/files#diff-2ae5224a8073d5cd24ce33fe39d5bfa8R45 on mac host

generating SHA256_SUM for release packages
find: -printf: unknown primary or operator

@girishramnani girishramnani changed the title [Merge immediately before release]: changed the release extension from .gz to .tar.gz changed the release extension from .gz to .tar.gz Aug 23, 2019
@girishramnani girishramnani changed the title changed the release extension from .gz to .tar.gz change the release extension from .gz to .tar.gz Aug 23, 2019
@openshift-ci-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kadel

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@amitkrout
Copy link
Contributor

@amitkrout no we cannot merge it right now because the documentation would say odo.tar.gz which will only happen until next release. So from the time we merge this to the next release, the docs would be inconsistent

can we split this into two PRs? On that updates scripts, we can merge it now. And the other that will update just docs, that we can merge after the release?

It should not effect the released version doc of for example beta4 because the patching is done against master branch until the next release.
Can you point out which doc and the references reflect the changes

@girishramnani I have tested it on my macOS and found here are no SHA256 SUM for the release packages. Can you please have a look

Please address this too

@amitkrout I don't have a macOS machine to reproduce this. Can you help me get more information on this?

On fedora no such issue occurred. The error is coming from line https://github.com/openshift/odo/pull/2009/files#diff-2ae5224a8073d5cd24ce33fe39d5bfa8R45 on mac host

generating SHA256_SUM for release packages
find: -printf: unknown primary or operator

Thanks for sharing the link.
-printf is not supported in OSX (macOS) causing the issue. cc_ @kadel

@girishramnani
Copy link
Contributor Author

Which means this wasn't working since a long time, we can resolve that later and open an issue for it for now. Thoughts?

@amitkrout
Copy link
Contributor

Which means this wasn't working since a long time, we can resolve that later and open an issue for it for now. Thoughts?

If the fix is a complex one then i will in the favor of later fix (After GA), otherwise fix it before GA. @kadel WDYT ?

@kadel
Copy link
Member

kadel commented Aug 26, 2019

@amitkrout It is ok if this script doesn't work on Mac. It is meant to be run on Linux only. It is just for CI. BTW, if you want to run this on Mac, you still can just install GNU find brew install findutils --with-default-names

@amitkrout
Copy link
Contributor

amitkrout commented Aug 27, 2019

@amitkrout It is ok if this script doesn't work on Mac. It is meant to be run on Linux only. It is just for CI. BTW, if you want to run this on Mac, you still can just install GNU find brew install findutils --with-default-names

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. Required by Prow. label Aug 27, 2019
@openshift-merge-robot openshift-merge-robot merged commit c23e542 into redhat-developer:master Aug 27, 2019
cdrage added a commit to cdrage/odo that referenced this pull request Sep 3, 2019
- Lists all URLs even if they are undeployed or not
(redhat-developer#2034)

- Added json output for `odo project delete -o json`
(redhat-developer#2037)

- Fixed service integration test that was previously failing
(redhat-developer#2022)

- `odo push` will now only push changed files
(redhat-developer#2030)
- We now use relative paths within the file indexer
(redhat-developer#2003)
- You can now create list and edit services using --app and --project
(redhat-developer#2001)
- Deleted files will now propagate to the OpenShift container
(redhat-developer#1999)
- Added `odo service create --context` functionality
(redhat-developer#1997)
- Making cross-compile independant of gox vendor package
(redhat-developer#2047)
- `odo-supervisord-image` has been renamed to `odo-init-image`
(redhat-developer#2027)
- Releases now use .tar.gz (redhat-developer#2009)
- If there is an error creating a service, it will fail quicker
(redhat-developer#2008)

- We now have a Google Group!
(redhat-developer#2007)
- Added documentation on how to manage environment
variables(redhat-developer#2026)
- Badges added to the README
(redhat-developer#2060)
- Updated documentation on uninstallation
(redhat-developer#2053)
- Added documentation for default parameters
(redhat-developer#2038)
- Minor update to help output
(redhat-developer#2006)
- Updated documentation regarding bootstrapper image
(redhat-developer#1991)
@cdrage cdrage mentioned this pull request Sep 3, 2019
openshift-merge-robot pushed a commit that referenced this pull request Sep 3, 2019
- Lists all URLs even if they are undeployed or not
(#2034)

- Added json output for `odo project delete -o json`
(#2037)

- Fixed service integration test that was previously failing
(#2022)

- `odo push` will now only push changed files
(#2030)
- We now use relative paths within the file indexer
(#2003)
- You can now create list and edit services using --app and --project
(#2001)
- Deleted files will now propagate to the OpenShift container
(#1999)
- Added `odo service create --context` functionality
(#1997)
- Making cross-compile independant of gox vendor package
(#2047)
- `odo-supervisord-image` has been renamed to `odo-init-image`
(#2027)
- Releases now use .tar.gz (#2009)
- If there is an error creating a service, it will fail quicker
(#2008)

- We now have a Google Group!
(#2007)
- Added documentation on how to manage environment
variables(#2026)
- Badges added to the README
(#2060)
- Updated documentation on uninstallation
(#2053)
- Added documentation for default parameters
(#2038)
- Minor update to help output
(#2006)
- Updated documentation regarding bootstrapper image
(#1991)
openshift-merge-robot pushed a commit that referenced this pull request Sep 13, 2019
* change .gz to .tar.gz in docs

* resolved the command
@rm3l rm3l added the estimated-size/S (5-10) Rough sizing for Epics. Less then one sprint of work for one person label Jun 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. Required by Prow. estimated-size/S (5-10) Rough sizing for Epics. Less then one sprint of work for one person lgtm Indicates that a PR is ready to be merged. Required by Prow.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Change release format from gzip to tar gz.
7 participants