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

Update to also publish to Azure Static Sites #2378

Merged
merged 5 commits into from
Sep 19, 2024
Merged

Update to also publish to Azure Static Sites #2378

merged 5 commits into from
Sep 19, 2024

Commits on Sep 19, 2024

  1. 🔧 (main.yml): add AzureSitesEnvironment variable and GitHub App token… 

    … for deployment

Introduce the AzureSitesEnvironment variable to manage different deployment environments (e.g., preview, canary). This change allows for more flexible and environment-specific deployments. Additionally, add steps to create a GitHub App token and use it for deploying static web apps to Azure, enhancing security and automation in the deployment process.
    @MrHinsh
    MrHinsh committed Sep 19, 2024
    Configuration menu
    Copy the full SHA
    4b8c9d9 View commit details
    Browse the repository at this point in the history

  2. 🔧 (main.yml): add additional Jekyll build step and upload artifact 

    Add a new step to build the site with Jekyll into a different directory (`./_site2/`) and upload it as a separate artifact. This allows for parallel builds or testing different configurations without interfering with the primary build. The commented-out Jekyll build action is retained for potential future use.
    @MrHinsh
    MrHinsh committed Sep 19, 2024
    Configuration menu
    Copy the full SHA
    3eab963 View commit details
    Browse the repository at this point in the history

  3. 🔧 (main.yml): update GitHub Actions workflow to download and deploy n… 

    …ew artifact

Add a step to download the AzureDevOpsMigrationTools-Site2 artifact and update the deployment path to use the new artifact. This ensures the correct version of the site is deployed, improving the deployment process and maintaining consistency with the latest build artifacts.
    @MrHinsh
    MrHinsh committed Sep 19, 2024
    Configuration menu
    Copy the full SHA
    93a233c View commit details
    Browse the repository at this point in the history

  4. 🔧 (main.yml): add baseurl parameter to Jekyll build command 

    Adding the `--baseurl "/"` parameter ensures that the site is built with the correct base URL, which is essential for proper linking and resource loading in the production environment. This change helps avoid issues related to incorrect paths when the site is deployed.
    @MrHinsh
    MrHinsh committed Sep 19, 2024
    Configuration menu
    Copy the full SHA
    0c5a334 View commit details
    Browse the repository at this point in the history

  5. 🔧 (main.yml): update Jekyll build command to use an empty baseurl 

    The baseurl parameter is set to an empty string to ensure that the site builds correctly without appending any base URL. This change is necessary to avoid potential issues with URL paths when deploying the site.
    @MrHinsh
    MrHinsh committed Sep 19, 2024
    Configuration menu
    Copy the full SHA
    6ce0236 View commit details
    Browse the repository at this point in the history