Github page build failure with no relevant error log - build

I am able to build and serve my jekyll blog locally without any error, but when I push the newer changes, I am getting page build failure error from Github.
The page build failed with the following error:
Page build failed. For more information, see https://help.github.com/articles/troubleshooting-github-pages-build-failures.
For information on troubleshooting Jekyll see:
https://help.github.com/articles/troubleshooting-jekyll-builds
Here github repo in question: https://github.com/prodicus/tasdikrahman.me/

For your local build, you must update gems with a bundle update. You will see that you have an 'highlighter' warning.
About github-pages. I've just forked your repo and it builds (with very small modifications) only with the same highlighter warning :
The page build completed successfully, but returned the following warning:
You are attempting to use the 'pygments' highlighter, which is currently unsupported on GitHub Pages. Your site will use 'rouge' for highlighting instead. To suppress this warning, change the 'highlighter' value to 'rouge' in your '_config.yml' and ensure the 'pygments' key is unset. For more information, see https://help.github.com/articles/page-build-failed-config-file-error/#fixing-highlighting-errors.
Can You try to change highlighter to rouge ?

Related

Sentry Expo: release will not upload index.android.bundle

In short: why index.android.bundle is not uploaded to Sentry server following expo's guide
I made a GitHub issue as I tested this with a clean repository. And there I specified the issue better and with more detail. The main problem could be the script I'm using. I will link the issue here:
https://github.com/expo/sentry-expo/issues/313
Hello.
I'm using the latest sentry-expo which correctly sends errors to sentry server.
I have followed the documentation from https://docs.expo.dev/guides/using-sentry/#uploading-source-maps-for-updates
On new builds index.android.bundle and .map is uploaded to sentry.
But when I make an update running eas update and following the sentry-cli releases... script as documented in expo guide, the android-'hash'.map file is uploaded and index.android.bundle is not.
Therefore dist is different between .js and .map file and Sentry issues don't contain source map information:
Source code was not found (see Troubleshooting for JavaScript)
Url app:///index.android.bundle
But if I change index.android.bundle to index.android.bundle.js in Sentry-cli --rewrite command the bundle is uploaded but issues still show the same information probably due to that android Archive is ~/index.android.bundle.js but the issue is expecting ~/index.android.bundle.
package versions:
"#sentry/react-native": "4.9.0",
"expo": "~47.0.8",
"sentry-expo": "~6.0.0",
I add here that I'm on Windows and couldn't get sentry-cli release to work as it is documented in expo-sentry tutorial. I used this script
cross-env ./node_modules/#sentry/cli/bin/sentry-cli releases --org 'organization name' --project 'project name' files 'release name' upload-sourcemaps --dist 'Android Update ID' --rewrite dist/bundles/index.android.bundle dist/bundles/android-'hash'.map
Thank you for all the help!
Android*.js file simply needed to be changed to index.android.bundle not to index.android.bundle.js. Now source maps are showing correctly.
Expo documentation showed everything correctly but my own understanding added the need of .js in file naming. Bundle file without any extension works correctly

Unable to create patch baseline with alternate repository for ubuntu

I wanted to create a patchbaseline which passes the alternative repo for ubuntu. I followed the info here. I set all other options as default in the ui and change the configuration to below:
[main]
name=ubuntutest
baseurl=http://security.ubuntu.com/ubuntu
enabled=1
But, I am getting the below error :
ValidationException: Source test did not contain a repository
specification, Source test configuration blob has an error in line 1.
I tried similarly for RHEL patch baseline (with different repo) and got the same errors.I could not find much examples to try online to confirm if i am giving the correct configuration. Can you please help me on how i can create patch baselines with alternative repositories?

Google Cloud Build Reject build failed with error: Build {build-id} might not have been rejected: Precondition check failed

I would like to reject old builds from the Google Cloud Build console. When I use the console following the instructions from the documentation, I receive an error:
Build {build-id} might not have been rejected: Precondition check failed.
I have tried to cancel the build. It gives me a generic error response:
The attempted action failed, please try again.
Tracking number: {tracking number}
I have tried using the gcloud command:
NOT_FOUND: Requested entity was not found
However, the build is still in the Cloud Build console.
I reproduced your case, I was able to reject/cancel builds which were pending approval.
Steps I followed,
First you have to create trigger builds, by providing all the
information as mentioned in this documentation .
I selected, Event as push to branch, source as USERNAME/cloud-build-samples(GitHub App), branch : ^main$,
configuration : Cloud Build configuration file (yaml or json),
location: Repository, Cloudbuild configuration file location: quickstart-automate/cloudbuild.yaml
Check the box of Approval to configure build triggers which require
approval before the build executes.
After your build trigger is ready, commit a change to your cloned
cloud-build-samples repository on your own GitHub account by updating
your source code and then Commit your changes to GitHub by running
the following commands:
git add quickstart-automate/main.go
git commit -m "update text"
git push
You may be prompted to enter your credentials when pushing code to your repository. If prompted, enter your username and authentication token that you generated from your GitHub account. You have now pushed a change to your repository. Your push will result in an automatic build by your trigger.
Now provide the gcloud commands to reject this pending approval
trigger build.
gcloud alpha builds reject BUILD_ID --project=PROJECT_ID \
Note : BUILD_ID is present in the Execution details of that particular build. Click on the specific trigger with build number, check the build details, you will find Build id. Use this build id in the gcloud command for rejecting pending builds.
After running the command, the build was rejected and the console UI
showed the same.
Also I tried rejecting the pending builds using the console/UI that
worked too.
Check this documentation when you see 4xx errors.

Why am I getting this error in AWS Device farm? Tests skipped due to test package parsing error. Please check Parsing result for more details

In AWS Device Farm, I created a new run. I chose native application. I uploaded my APK. I chose Calabash as the tests. I got this error message:
Tests skipped due to test package parsing error. Please check Parsing result for more details.
I downloaded the Parsing result. Here's what it said:
Failed to run cucumber dry-run command. See the information below for more details.
Here are the contents for the Parsing result:
'cucumber --dry-run --format json --out /tmp/scratchvxnAeX.scratch/tmpF6f5Xx' failed.
Could not find proper version of cucumber (2.99.0) in any of the sources
Run `bundle install` to install missing gems.
Solution
I have some .rb page objects. I added require 'calabash-android' to the top of those files. Then I made a new run and ran it. It worked.
How I got to the solution
Through Google I came across CALABASH_TEST_PACKAGE_DRY_RUN_FAILED here.
Running this command failed: cucumber-ios --dry-run --format json features
I figured that was for ios. So I tried this: bundle exec calabash-android run .\app-releaseStaging.apk --dry-run. I got this error:
uninitialized constant Calabash::ABase (NameError)
I wasn't getting that error when running locally.
According to this:
-d, --dry-run Invokes formatters without executing the steps. This also omits the loading of your support/env.rb file if it exists.
I had require 'calabash-android' inside env.rb. So I moved it to my page objects. Then it worked.
You may find the aws-device-farm-calabash-tests-for-sample-app useful.

Error in cloudbees build: unable to find pom.xml

When I build my cloudbees project it gives the following error:
ERROR: No such file /scratch/jenkins/workspace/glassfish-myruby/pom.xml
Where my project name is glassfish-myruby.
Go to the job you created and click on the "Workspace" link on the left. This will show you how your project was checked out. The pom may be in a different place than you expect.
I ran into a similar problem. My project was building fine, then suddenly stopped with the same error:
Parsing POMs
ERROR: No such file /scratch/jenkins/workspace/MyMoney/pom.xml
Perhaps you need to specify the correct POM file path in the project configuration?
[cloudbees-deployer] Skipping deployment as build result is FAILURE
Finished: FAILURE
I realized the only thing I had changed was adding a GitHub page (as described in http://pages.github.com/)
For reasons I don't understand, this was causing my project to check out from the gh-pages branch instead of master, as reflected in the console output:
Commencing build of Revision 88d8d7ee822e02aa2cdae11e07265eb7a8403fed (origin/gh-pages)
This was also reflected in the jenkins workspace (it contained the GitHub pages files, rather than my project files).
I'm sure there is a way to get this to work AND use GitHub pages, but for me the GitHub page was just an experiment, so I deleted the branch using:
git push origin --delete gh-pages
I then also did another commit to make sure all was OK and rebuilt.
The project is now checking out from master again and building OK.