Publish content

This article explains how to preview content on experienceleague.corp.adobe.com, how to publish (or activate) content manually, and how to configure your repo to auto-activate. We use “publish” and “activate” synonymously.

Publishing content works on a repo level. You cannot publish only individual articles or guides.

Preview content

When you successfully commit changes to the master branch, the changes are pushed to experienceleague.corp.adobe.com for preview. View the Slack summary for a list of preview links.

slack notification

If validation fails, your updates will not be available for preview until validation succeeds.

Activate content from Slack

If validation succeeds, the Slack summary displays either a Publish or a Publish Now button, depending on whether auto-activate is enabled in your repo.

  1. In the Slack summary, click Publish or Publish Now.

  2. If necessary, sign in to Jenkins (VPN or Corp required).

    If you’re a contractor, you might need to get access rights. Contact IT to request to add http://docs.ci to the list of approved servers for the “Vendor_Basic” VPN.

  3. Click Build to run the activate job for the repo.

You’ll get a Slack notification when the activation job is complete.

Activate content by running a Jenkins job

You can activate content by running the activate-exl job in Jenkins. When you run this job, all content is automatically activated, including articles, assets, and the TOC.

The changes should go live on experienceleague.adobe.com as soon as the job has completed.

  1. Make sure that the production job with the most recent commit to master is complete.
  2. Go to Jenkins and open the activate-exl job.
  3. Click Log In in the upper right corner and sign in using you Adobe LDAP account.
  4. Click Build with Parameters.
  5. Choose the repo and language, and click Build.

activate exl

If your repo does not appear in the pulldown menu, contact Bob. (Or, click Configure and add your repo name without .en).

Landing pages cannot be manually activated. If landing page validation passes, changes go live on the 2-hour publishing schedule.

IMPORTANT

As a rule, don’t commit to master unless you’re ready to activate the content soon after previewing it.

There is no connection between activating English and localization repos. Localization repos are configured to auto-activate. If you commit to master successfully but don’t activate, your changes will go live in other languages.

Set up your repo to auto-activate

You can configure a repo so that content is automatically activated on a successful push to production. We recommend that you turn this on only after you’re comfortable with the new workflow.

  1. Go to your repo’s exl job and sign in.
  2. Click Configure.
  3. Scroll down and locate the AUTOACTIVATE parameter. Select the Default value check box.
  4. Click Save.

auto activate

The next time you commit to master, after validation passes, your edits will automatically be published to experienceleague.adobe.com when the next pickup occurs (currently every two hours). See the next section for the publishing schedule.

TIP

If you want your changes to go live immediately, run the activate-exl job.

Publishing Schedule

Auto-activated content is published thirty minutes past every odd hour PST. So if you publish your content at midnight PST, you can expect it to be published shortly after 01:30 PST. The following table provides an overview for our worldwide authors.

Time Zone Schedule
PST Odd hours on the half hour
MST Even hours on the half hour
EST Even hours on the half hour
GMT Odd hours on the half hour
CET Even hours on the half hour
EET Odd hours on the half hour
IST Odd hours on the hour
NOTE

The schedule is based on PST. Therefore when the US begins/ends DST (second Sunday of March/first Sunday of November), this schedule will shift for the rest of the world that observes DST later/earlier and for those that do not observe DST at all.

TIP

If you need your changes to go live sooner than scheduled, run the activate-exl job.

Pipeline overview

Here’s some background info for the EXL pipeline.

Hooking up a repo to the pipeline (admin)

To hook up a repo to the EXL pipeline:

  • Run GenerateExlJob in Jenkins to add the repo to the EXL pipeline. Once this job is run, the repo should appear here: Jenkins EXL. (SCCM/Bob)
  • Add repo (and all language repos) to Airtable. (SCCM/Bob)
  • Add and configure public mirror. (SCCM/Bob)
  • Add webhook for Acrolinx. (SCCM/Bob)
  • Turn on Publish flag in Airtable to allow publishing. (SCCM/Bob)

See Creating and configuring repositories.

What happens when a repo is updated?

When you commit changes to the master branch of a repo that is connected to the pipeline, the following actions occur:

  • The public mirror on github.com/adobedocs/<repo-name> is updated.
  • The localization repos are updated, and machine translation is triggered.
  • Content is validated in Jenkins. See Validation.
  • If validation succeeds, content is packaged and uploaded to an Azure server. That package is processed and rendered into HTML for preview on experienceleague.corp.adobe.com.
  • If the repo is set to auto-activate, the changes will go live on experienceleague.adobe.com in the next pickup that occurs every two hours. If you run the activate-exl job in Jenkins, the content goes live to production as soon as that job finishes.

On this page