fix: Release scripts Python version (#24544)

This commit is contained in:
Michael S. Molina 2023-06-28 11:40:10 -03:00 committed by GitHub
parent 262b769d19
commit a90f740a81
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
6 changed files with 10 additions and 7 deletions

View File

@ -14,7 +14,7 @@
# See the License for the specific language governing permissions and
# limitations under the License.
#
FROM python:3.8-buster
FROM python:3.9-buster
RUN useradd --user-group --create-home --no-log-init --shell /bin/bash superset

View File

@ -14,7 +14,7 @@
# See the License for the specific language governing permissions and
# limitations under the License.
#
FROM python:3.8-buster
FROM python:3.9-buster
RUN useradd --user-group --create-home --no-log-init --shell /bin/bash superset

View File

@ -14,7 +14,7 @@
# See the License for the specific language governing permissions and
# limitations under the License.
#
FROM python:3.8-buster
FROM python:3.9-buster
ARG VERSION
RUN git clone --depth 1 --branch ${VERSION} https://github.com/apache/superset.git /superset

View File

@ -14,7 +14,7 @@
# See the License for the specific language governing permissions and
# limitations under the License.
#
FROM python:3.8-buster
FROM python:3.9-buster
RUN apt-get update -y
RUN apt-get install -y jq

View File

@ -74,7 +74,7 @@ the repo directly from the main `apache/superset` repo to a new directory `super
```bash
cd <MY PROJECTS PATH>
git clone git@github.com:apache/superset.git superset-release
git clone https://github.com/apache/superset.git superset-release
cd superset-release
```
@ -102,7 +102,7 @@ the same terminal session won't be used for crafting the release candidate and t
final release. Therefore, it's a good idea to do the following every time you
work on a new phase of the release process to make sure you aren't releasing
the wrong files/using wrong names. There's a script to help you set correctly all the
necessary environment variables. Change your current directory to `superset/RELEASING`
necessary environment variables. Change your current directory to `RELEASING`
and execute the `set_release_env.sh` script with the relevant parameters:
Usage (MacOS/ZSH):

View File

@ -19,7 +19,10 @@ set -ex
echo "[WARNING] this entrypoint creates an admin/admin user"
echo "[WARNING] it should only be used for lightweight testing/validation"
if $SUPERSET_TESTENV then echo "SUPERSET IS RUNNING IN TEST MODE"
if [ -z "${SUPERSET_TESTENV}" ]; then
echo "SUPERSET IS RUNNING IN TEST MODE"
fi
# Create an admin user (you will be prompted to set username, first and last name before setting a password)
superset fab create-admin \